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

Annotations already cover read-only and idempotency, but the description adds real behavior: bounded pages, parent-special context, listening/transcript links, and explicitly no media URLs. The caution that "metadata matches do not prove spoken content" is a genuinely useful caveat an agent could not infer from 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?

Four dense sentences, front-loaded with the core matching rule before caveats and return-shape notes; no filler. Minor friction from naming "nextOffset", a response field rather than the actual offset input, which makes the continuation sentence slightly less crisp.

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?

Return values are partly described and an output schema exists, so that burden is covered. Since all five parameters are optional, the one meaningful gap is what happens when query is omitted — whether it lists broadly or fails — which the description does not clarify.

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?

With 0% schema description coverage, the description carries the load and mostly succeeds: it explains that matching is literal keyword based, that specialId/comedianId are optional narrowing scopes drawn from prior results, and that pagination continues via the offset mechanism. It leaves the limit parameter's meaning and bounds unaddressed.

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?

"Find individual tracks" states a specific verb and resource, and the qualifier "by literal keywords in track/special titles or comedian names" pins down the matching surface. It is clearly separable from siblings like search_comedy_specials or get_comedy_track, which retrieve other entity types or a single known track.

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?

It gives a clear use context (keyword lookup, optionally narrowed within a previously returned specialId or comedianId) and an explicit continuation rule ("Continue with nextOffset and unchanged filters"). It stops short of naming when to prefer a sibling, e.g. when a track ID is already known and get_comedy_track would be better.

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