tvmaze_search

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

The annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds no further behavioral context such as result ordering, pagination, rate limits, or what happens with ambiguous names, so it contributes essentially nothing beyond the 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 description is a single efficient sentence with the purpose front-loaded. It is appropriately sized for a simple search tool, though it could include one routing note without becoming verbose.

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?

For a simple one-parameter search with complete schema coverage and safety annotations, the definition is minimally adequate. It omits what the search returns, whether multiple matches are possible, and how it relates to the sibling detail tool, leaving some ambiguity for an agent choosing among TV-related tools.

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 coverage is 100% for the single 'query' parameter, and the schema itself documents it as 'Show name to search for.' The description's phrase 'by name' aligns with the schema but adds no extra syntax or format guidance, which is acceptable given high schema coverage.

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 clear verb and resource: 'Search for TV shows by name.' An agent can distinguish it from tvmaze_show and tvmaze_schedule at a high level, though it does not explicitly name those siblings or clarify the boundary between search and detail lookup.

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?

There is no explicit guidance on when to use this instead of tvmaze_show or tmdb_search_tv. The search purpose is implied, but the description provides no exclusions, alternatives, or contextual triggers.

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