list_search_podcast

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds only the HTTP method (GET), which is redundant. It does not disclose expected response format, pagination, or any other behavioral traits, providing minimal extra value beyond 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 very short, essentially a single sentence plus the endpoint. It is front-loaded with the basic purpose but is too terse to be considered well-structured for an agent, lacking essential context while remaining efficient in length.

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?

Despite having an output schema, the description does not explain what the search returns or how it behaves with no parameters. For a 'search podcast' tool, it's unclear whether this searches by title, returns all podcasts, or requires hidden query parameters. The description is insufficient for an agent to understand the tool's capabilities.

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 tool has zero parameters and an empty input schema. Per calibration, the baseline for 0 params is 4. The description needs no parameter explanation since none exist, and it neither adds nor detracts from 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 'Get search podcast' which identifies a verb and resource, distinguishing it from sibling search tools for authors, books, etc. However, it is vague about what exactly is searched (podcasts vs. episodes) and lacks specificity about the search's scope or outcome.

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?

No guidance is given on when to use this tool versus alternative search tools like list_search_books or list_search_authors. The description only provides the endpoint without any conditions, typical use cases, or exclusions, leaving the agent without context for tool selection.

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