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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, so the description doesn't need to restate those. It adds valuable behavioral context: the atomic two-step action, audit logging of the move, and the refusal condition with force=true. It doesn't mention failure modes or side effects beyond the refusal, but the audit-log note and force semantics go beyond the 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?

Three sentences, each with a distinct job: what the tool does, when it refuses, and what to do next. No filler, no repetition of schema details. The most important behavioral constraint (refusal unless force=true) is front-loaded in the second sentence.

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?

For a mutation tool with no output schema, the description covers the core behavior, the refusal condition, and the follow-up workflow. It doesn't describe the return value or error format, but the annotations already cover the safety profile (not read-only, not idempotent, not destructive). The only minor gap is not stating what happens on success (e.g., returns the updated ticket), but the workflow guidance compensates.

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 67% (ticket_id and assignee are described; force is described in the schema too, so actually all three are described). The description adds meaning by explaining that assignee is 'your agent name' and that force=true means 'take over a ticket another agent holds', which clarifies the parameter's purpose beyond the schema's terse description. The description also ties assignee to the claim action, adding context the schema alone doesn't provide.

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 action ('Claim a ticket to work on'), the resource (ticket), and the two-step behavior (sets assignee, moves to in_progress). It also distinguishes itself from related ticket tools by naming the follow-up tools (ticket_comment, ticket_update) and the force behavior. This is a specific verb+resource with clear scope.

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 explicitly says when to use it ('Claim a ticket to work on'), when it refuses (if another agent has it in progress unless force=true), and what to do after (follow up with ticket_comment and finish via ticket_update). It also implies the alternative (ticket_update) for status changes, giving clear context and exclusions.

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