get_show_details

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

With no annotations provided, the description carries the transparency burden. It reveals that the operation is a fetch, describes the metadata categories, and notes the default 'concise' prose output. However, it does not mention error behavior, authentication needs, or what happens when a show_id is invalid.

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 compact and front-loaded, with the core action in the first sentence and the default format in the second. The parenthetical field list is useful but slightly redundant with the phrase 'full metadata'.

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?

The description plus schema is enough to make a basic call, and the response_format parameter addresses output shape. However, without an output schema and with many sibling get_* tools, the description would be stronger if it explicitly separated this tool from get_show or get_show_episodes.

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%, so the parameters are already well documented. The description adds some meaning by framing the output as prose vs. raw data via response_format, but it does not meaningfully extend beyond the schema's existing parameter descriptions.

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 names a specific action and resource: 'Fetch full metadata for one show', and lists example fields. It is clear on its own but does not explicitly distinguish it from the sibling tool 'get_show', so it falls short of a 5.

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 implies the tool is for single-show metadata lookup and notes the default output mode, but it gives no explicit guidance on when to use this tool instead of alternatives like get_show, get_show_episodes, or get_episode. Usage is inferable, not stated.

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