Search media

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

Annotations already declare readOnlyHint=true, and the description is consistent with that. It adds genuinely non-obvious context beyond the annotations: that indexer results carry attacker-controllable release names and come wrapped in an explicit untrusted-data boundary, which is a safety-relevant behavioral trait an agent should know before trusting returned strings.

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 sentences with no filler; the scope statement comes first and the security caveat second. Every clause carries information the agent needs.

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 a full input schema, an output schema, and readOnlyHint already present, the description only needs to supply scope and the trust caveat, and it does both. The remaining gap is sibling routing advice against lookup_media and discover_media, which the description leaves unaddressed.

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 query, limit, offset, detail, and source are all documented in the schema, including the untrusted-data note on source. The description adds no parameter-level detail beyond what is already structured, 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 names three concrete scopes: existing library, metadata for titles not owned, and indexer offerings. That scope statement implicitly separates it from get_library and discover_media, but no sibling is named explicitly, so differentiation still requires the agent to infer from the source enum.

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 three-scope framing implies when each mode applies and the schema's source enum spells out library/discover/indexers. However, there is no explicit guidance on when to pick search_media over lookup_media, discover_media, or get_library, and no exclusions or prerequisites are stated in the description itself.

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