omdb_by_title

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, covering the safety profile. The description adds only that the resource is a movie/show and retrieval is by title, without disclosing rate limits, API-key requirements, or return behavior. That is acceptable but adds little beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and has no filler. It is appropriately concise, though its brevity contributes to the missing usage and parameter detail rather than serving a complete definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, four parameters are undocumented by the schema, and the description does not fill that gap. An agent is left without guidance on optional filters, authentication, or what the response contains, which is insufficient for a four-parameter lookup tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for four parameters. The description only hints at the required title parameter ('by title') and vaguely at media type ('movie/show'), but does not explain the year filter or the api_key parameter. With low coverage, the description should compensate but does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Get an OMDB movie/show') and narrows retrieval to 'by title'. It is clear what the tool returns, but it does not explicitly distinguish itself from the sibling tools omdb_search and omdb_by_id.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no guidance on when to use this tool instead of omdb_search or omdb_by_id. It implies title-based lookup but does not state prerequisites, exclusions, or alternative-selection conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.