bulk_update_issues

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

No annotations provided. Description lists actions but does not disclose behavioral traits such as destructive nature, authentication needs, rate limits, or whether changes are reversible.

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 sentences with no wasted words. Front-loaded with main purpose.

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?

Despite full schema coverage, description lacks completeness: doesn't explain that query selects issues for bulk update, or that assigned_to requires specific format. For a mutation tool, more context on scope and side effects would be needed.

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 3. Description does not add significant meaning beyond schema descriptions; no extra context on query format or assignment syntax.

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 'Bulk update multiple issues at once' and lists actions: resolve, ignore, unresolve, assign. This distinguishes it from siblings like update_sentry_issue_status which likely updates a single issue.

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?

Says 'Useful for triaging many issues', implying when to use, but does not explicitly state when not to use or name alternatives like single update.

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