tag_bulk_association

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

Description only says 'adds tags', implying mutation, but does not disclose whether it appends, replaces, or merges tags. No info on side effects, permissions, or idempotency. With no annotations, this is insufficient.

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?

Single sentence is concise and front-loaded, but at the cost of omitting important details. Still earns a 4 for efficiency.

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, no mention of partial success, error handling, or format of story objects. Among many sibling tools, this description does not help the agent decide when to use this specific bulk association tool.

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?

Input schema covers 100% of parameters with descriptions. Tool description adds no extra meaning beyond what the schema provides, so baseline 3.

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 action: adding tags to multiple stories. It uses specific verb and resource, but does not explicitly differentiate from other tag-related operations like bulk_update_stories which might also modify tags.

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 versus alternatives (e.g., create_tag, update_tag) or when not to use it. No prerequisites mentioned, such as requirement that tags already exist.

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