Get movie status

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

No annotations are provided, so the description must disclose safety and behavioral traits. It mentions getting status/history/collections but does not state if the operation is read-only, needs authentication, or what the response contains. This is minimal behavioral context.

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, concise sentence with no wasted words. It is efficient but could benefit from additional structural elements like bullet points for clarity without being lengthy.

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 the simplicity (one parameter, no output schema), the description is incomplete. It does not explain the return structure of status/history/collections or how to interpret the results, leaving gaps for the agent.

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?

With 0% schema description coverage, the description should clarify the parameter. It mentions 'by metadataId' but does not explain what metadataId refers to or how to obtain it. The agent lacks guidance on the parameter's semantics beyond its name.

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 it gets 'status/history/collections for a movie by metadataId', with a specific verb and resource. The name 'ryot_get_movie_status' distinguishes it from siblings like ryot_get_show_status and ryot_get_game_status, making the purpose unambiguous.

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 indicates the required parameter (metadataId) but does not provide guidance on when to use this tool versus alternatives like ryot_get_show_status. There is no explicit 'when-not' or mention of context for usage.

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