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

No annotations are provided, so the description carries full responsibility for disclosing behavior. It does not mention that this is a read-only operation, whether authentication is required, or how errors (e.g., invalid episode_id) are handled. It only lists returned fields, leaving behavioral traits undisclosed.

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 sentence, concise and front-loaded, listing the key output fields without any filler. Every word contributes to the tool's purpose, making it highly efficient.

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 tool is simple with one parameter, but without an output schema, the description should clarify the response structure. While it lists fields, it does not explain what 'podcast info' includes or how this differs from get_episode_full. The description is adequate but leaves some ambiguity about the full response and relationship to siblings.

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 parameter episode_id, described simply as 'Episode ID' in the schema. The description adds minimal meaning by referring to 'a specific episode,' but does not elaborate on format, source, or validation rules. Baseline 3 applies due to full 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 clearly states the tool retrieves metadata for a specific episode and enumerates the specific fields returned (title, publish date, duration, sentiment scores, podcast info). This distinguishes it from siblings like get_episode_summary or get_episode_transcript, which likely handle other content types.

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 for metadata retrieval but does not explicitly state when to use this over alternatives like get_episode_full or get_episode_summary. There is no mention of exclusions or prerequisites, so the guidance is inferred from the name and field list rather than stated.

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