Get metadata details

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

No annotations provided. The description does not explicitly state the tool is read-only, nor does it disclose error handling, rate limits, or authentication requirements. The word 'Get' implies no side effects, but fails to confirm.

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, front-loaded sentence with no wasted words. While not structured as bullet points, it is appropriately concise for a simple tool.

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?

Given no output schema and a single parameter, the description should at least hint at what metadata details are returned (e.g., fields like title, genre, rating). It fails to provide that context, leaving the agent guessing about the output.

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%, yet the description only restates the parameter name 'metadataId' without explaining its format, source, or constraints. The agent gets no additional semantic value 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 clearly states the tool retrieves metadata details for various media types (movie/show/book/game/etc) by a metadataId, distinguishing it from sibling tools that focus on specific actions like adding to lists or marking status.

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 guidance on when to use this tool vs alternatives (e.g., ryot_get_user_metadata_details, ryot_get_movie_status). The description lacks context about prerequisites or when not to use it.

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