anilist_batch_update

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

Annotations already indicate destructive action, but the description adds value by explaining default dry-run mode ('preview only') and the need for ANILIST_TOKEN. No contradictions with annotations.

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?

Four sentences, front-loaded with purpose and usage examples. No redundant or missing information. Every sentence earns its place.

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?

The tool is complex with nested filters and actions, and no output schema is provided. The description mentions preview changes but does not explain the response format, which is a notable gap.

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 high (all parameters have descriptions in the schema), so baseline is 3. The tool description does not add parameter-level detail beyond examples, but the schema is clear.

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 verb ('Apply a bulk action') and resource ('multiple list entries matching a filter'), with concrete examples like moving low-scored titles to Dropped. It distinguishes from siblings by focusing on batch operations.

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 gives explicit when-to-use scenarios (e.g., bulk-change statuses) and notes the default dry-run mode and token requirement. However, it does not mention alternatives when not to use this tool (e.g., single updates).

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