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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful context beyond that by enumerating the returned fields (seq, name, owner, last publish time) even though no output schema exists, though it says nothing about result caps or ranking behavior beyond what the schema implies.

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?

Three short sentences, zero filler, with purpose stated first and the downstream hand-off last. Every sentence carries actionable information.

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?

With no output schema, the description compensates by naming the returned fields, and annotations carry the safety profile; pagination is handled entirely in the schema. Nothing essential is missing for a simple search tool, though a note on total-result behavior or empty-result handling would round it out.

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 100%, so page, pageSize and query are each documented in the schema with defaults and ranges. The description's 'by keywords' clarifies the query intent slightly but adds no format or syntax detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb (Search) and resource (podcasts/shows) scoped to Podwise keywords, and explicitly includes the return fields. It is cleanly distinguishable from search_episodes, which operates at the episode level rather than the show level.

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 tells the agent what to do with the result ('use the podcast seq with list_podcast_episodes or set_podcast_follow'), which routes it toward the correct follow-on siblings. It does not, however, state when to prefer this over search_episodes, so the podcast-vs-episode choice is left to inference from the name.

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