search

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

No annotations exist, so the description must carry the full disclosure burden. It mentions 'search' (read operation) but does not state read-only nature, destructive potential, authentication needs, or what happens on no results. Only minimal behavioral context is provided.

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 a single 6-word sentence, which is concise and front-loaded with the core purpose. However, it may be too terse; while it earns its place, it lacks sufficient detail for an effective tool description.

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 and no description of return values, pagination, or fields, the description is incomplete for a search tool. Given the parameter count and siblings, more context is needed to understand the tool's full behavior.

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 0%, meaning the description adds no meaning beyond the schema. The description only says 'Search for media', leaving parameters 'service', 'query', and 'limit' completely unexplained in terms of format, source, or usage.

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 'Search for media (series/movies) to add', clearly specifying the verb 'search', the resource 'media' with parenthetical clarification, and the intent 'to add'. It distinguishes from sibling tools like 'list_services' but could be improved by specifying what 'add' means (e.g., add to library).

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 explicit guidance on when to use this tool versus alternatives. The phrase 'to add' implies a use case, but sibling tools like 'add_new' suggest the actual addition step, and no exclusion criteria or context for choosing between search and other tools is provided.

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