bulk_tag_tickets

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

No annotations are provided, so the description carries the full burden. It discloses the dry-run default, which is a key behavioral trait. However, it does not mention authorization requirements, rate limits, or the impact of disabling dry-run (e.g., irreversible tagging).

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?

Two concise sentences that front-load the core purpose and a critical default behavior. No wasted 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?

Given the complexity of a bulk operation (3 params, output schema exists), the description is too minimal. It lacks explanation of output format, success/failure behavior, and potential side effects. Relies heavily on the output schema, which is not visible here.

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 0%, so the description must compensate. It explains 'query' and 'tags' as part of the search and tagging action, and mentions 'dry_run' default. However, no details on tag format, query syntax, or constraints, leaving significant gaps.

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 'tag' and the resource 'tickets matching a Zendesk search query', and includes the default dry-run mode. It distinguishes itself from sibling tools like bulk_close_tickets.

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 implies usage for tagging tickets based on a search query, but does not explicitly state when to use this tool vs alternatives or provide when-not conditions. No guidance on prerequisites or scenarios where dry-run should be disabled.

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