Discover media API

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

No annotations are provided, so the description bears full responsibility. It does not disclose whether the tool is read-only, requires authentication, or has any side effects. The phrase 'schema operations' hints at non-destructive activity but is not explicit.

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 sentence with no unnecessary words. However, it uses jargon like 'schema operations and fields' which may require clarification. Overall efficient but could be slightly clearer.

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 tool with one parameter and no output schema or annotations, the description is very minimal. It does not explain what the tool returns or how to use the limit parameter, leaving users guessing about functionality. Given sibling tools, it lacks sufficient detail to differentiate.

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?

Only one parameter (limit) is present in the schema with 0% description coverage. The description does not mention or explain the parameter's purpose or how it affects results, providing no additional meaning beyond 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?

The description specifies the verb 'Find' and the resource 'Ryot schema operations and fields' with a list of media categories. It is specific but does not fully distinguish from similar tools like ryot_schema_search or ryot_search_media, which may also involve discovering schema or media.

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 description provides context (media types it covers) but no explicit guidance on when to use this tool versus alternatives like ryot_game_discovery or ryot_search_media. No when-not or exclusion criteria are given.

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