get_movie_show_by_id

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

With no annotations provided, the description carries full burden. It states this is a retrieval operation but doesn't disclose behavioral traits like authentication requirements, rate limits, error conditions, or whether it's idempotent. The return format is mentioned but lacks detail on structure or potential null responses.

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 appropriately sized with three sentences. The first states the purpose, the second explains the parameter, and the third describes the return. No wasted words, though the colon-prefixed format is slightly unconventional.

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 retrieval tool with 1 parameter and no output schema, the description is minimally adequate. It covers purpose, parameter meaning, and return type, but lacks behavioral context (auth, errors, etc.) and doesn't fully address sibling differentiation given the server's multiple show-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 description coverage is 0%, but the description compensates by explaining the single parameter: 'The MyShows ID of the show or movie to retrieve.' This adds meaning beyond the schema's type declaration, though it doesn't specify format constraints or example values.

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 clearly states the tool's purpose: 'Retrieves a show or movie by its MyShows ID.' This is a specific verb ('Retrieves') and resource ('show or movie'), though it doesn't explicitly differentiate from siblings like 'search_shows' or 'get_myshows_profile_shows_list' beyond the ID-based 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?

The description implies usage when you have a specific MyShows ID, but doesn't explicitly state when to use this versus alternatives like 'search_shows' (for name-based queries) or 'get_myshows_profile_shows_list' (for user-specific lists). No exclusions or prerequisites are mentioned.

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