anilist_rate

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

Description adds token requirement and notes that scores display in user's preferred format, complementing annotations (destructiveHint=true, idempotentHint=true). No contradiction; aligns with rating mutation and removal behavior.

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?

Three concise sentences: purpose, usage, requirement. No unnecessary words. Front-loaded critical information.

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?

Covers all key aspects: what it does, how to use, token requirement, and behavior. No output schema needed; parameters and actions are well-explained.

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?

Both parameters (mediaId, score) are fully described in schema. Description adds valuable context: decimals supported, use 0 to remove, and score range clarification. Exceeds baseline.

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?

Description clearly states 'Score an anime or manga on your list' with specific verb and resource, and differentiates from siblings like anilist_add_to_list or anilist_update_progress by focusing solely on rating.

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?

Explicitly says 'Use when the user wants to give a rating (0-10)' and includes use of 0 to remove. While no alternatives are listed, the sibling context makes it clear this is for rating only.

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