get_shows_by_id

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, and the GET method is consistent with those. The description adds little behavioral context beyond the endpoint and an 'extended' response toggle, so it does not meaningfully go 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 brief and well-structured: a one-line purpose, the endpoint, and an Args list. Every line carries information, and nothing is repeated from the schema or annotations.

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 two-parameter read, the description is mostly sufficient, especially with an output schema and safety annotations available. The main gap is the unspecified semantics of 'extended' and the lack of guidance relative to the dozens of sibling show endpoints.

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?

The Args section provides minimal descriptions for both parameters, clarifying that id is an id/slug. However, 'extended' remains vague—no valid values or formats are given—and schema description coverage is 0%, so the description only partially compensates.

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?

"Get a single show." plus the explicit GET /shows/{id} endpoint names a specific verb, resource, and scope. This distinguishes the base show retrieval from the many get_shows_by_id_* siblings (seasons, related, comments, etc.) without ambiguity.

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 clear context: call it when you need one show identified by id/slug. It does not explicitly name alternative sibling tools for related data, so it lacks explicit exclusions, but the 'single show' framing is enough to route an agent in most cases.

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