Search TV shows

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

No annotations are provided, so the description must disclose behavior. It states it's a search (read operation) but doesn't mention pagination behavior, result format, or any restrictions. The default source is noted but no details on side effects or prerequisites.

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 very concise with two sentences and front-loaded purpose. It is efficient but could include more useful information without becoming verbose. Still, it earns a high score for structure.

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 3 parameters, no output schema, and no annotations, the description is incomplete. It lacks details on return values, pagination, and source usage. The minimal description fails to fully guide an agent in using this tool.

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?

The description only partially explains the 'source' parameter by noting defaults and alternatives. It provides no information about 'query' or 'page' parameters, leaving the agent to infer from the schema. Since schema has 0% description coverage, this is a significant gap.

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 clearly states 'Search TV shows in Ryot' with a specific verb and resource. It distinguishes from siblings like 'ryot_search_movie' and 'ryot_search_media' by targeting TV shows. The mention of default source adds specificity.

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 versus alternatives like 'ryot_search_media'. The description implies for TV show searches but doesn't provide context for selecting source or handling edge cases. Minimal usage direction.

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