anilist_unscored

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. Description adds that it lists from completed lists and returns sorted by most recently completed. No contradictions. Minor gap: doesn't specify behavior when no unscored titles exist.

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 short sentences, all essential. The core action is front-loaded. No redundant or unnecessary words.

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?

No output schema, but description explains that results are titles sorted by recency. For a simple list tool with clear annotations, this is sufficient. Could mention whether returns full details or just titles, but not critical.

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 coverage is 100%, so baseline is 3. Description adds value by noting username falls back to configured default, which is not in schema. Also restates limit default and max, reinforcing schema info. Good additional context.

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 the specific action: 'List completed anime or manga that haven't been scored yet.' This distinguishes it from siblings like anilist_list (general list), anilist_rate (scoring), and anilist_completionist (completion tracking).

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 when to use: 'when the user wants to catch up on scoring, find unrated titles, or do a batch scoring session.' Also provides context: 'Returns titles sorted by most recently completed.' Does not mention when not to use or alternative tools, but purpose is clear enough.

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