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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavior beyond that: which fields are indexed, what each returned show contains (slug, feed URL, page, playlist), and the 90-day freshness filter that silently excludes stale shows — a genuinely non-obvious selection rule.

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?

Two dense sentences that front-load the core operation, followed by the return shape and the freshness rule. The trailing 'Served by p0dcasters (https://p0dcasters.com/mcp)' line is boilerplate that adds little for an agent, but it is short.

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 two-parameter read tool with no output schema, the description covers search scope, result fields and the freshness filter, which is enough to call it correctly. Pagination beyond the limit cap (no offset/cursor) and result ordering are unstated, which is the only meaningful gap.

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 baseline is 3, but the description earns extra credit by explaining that the query string is matched against titles, descriptions, authors and domains — semantics the schema's bare 'What to search for' does not convey. The limit parameter's meaning is left entirely to the schema.

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 and resource ('Full-text search over the titles, descriptions, authors and domains of every podcast listed') and adds scope details: any host, plus the constraint that only shows with an episode in the last 90 days are listed. It never names a sibling such as p0dcasters_browse or p0dcasters_list_shows, so differentiation is left implicit.

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?

Usage is implied by the word 'search' and the required query parameter, but there is no explicit when-to-use or when-not guidance and no mention of the browse/list siblings as alternatives for exploring without a search term. An agent can infer intent but must reason about routing on its own.

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