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

Goes well beyond the annotations (idempotentHint=true, openWorldHint=true): it discloses re-read/refusal-on-change behavior, atomic all-or-nothing commit of tickets+links+receipt, that nothing is written to the provider, and the exact replay semantics of request_id. Also names required scopes (integrations:write, tickets:write).

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?

Six dense sentences, front-loaded with the action, then failure/replay behavior, then recovery guidance, then permissions. Each sentence conveys a distinct operational fact with no filler.

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 with no output schema, the description covers atomicity, idempotency, provider non-writes, and recovery. It does not describe the shape of the returned receipt object (partial vs full import, link counts), which an agent may want.

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 0%, so the description must carry parameter meaning. It explains request_id (fresh per import, replay on repeat) and implies fingerprint (refuses if anything changed since preview) and selection (previewed items), but provider/connection_id semantics are left to the schema/enum. It compensates only partially for a fully undocumented schema.

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?

States a specific verb and resource ('Import previewed items as new top-level backlog tasks') and clarifies the commit semantics versus the preview step. An agent can distinguish this from preview_ticket_integration_import and the receipt/effect readers without opening any schema.

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?

Gives clear operational context: use a fresh request_id per import, a repeated one replays the original receipt, and if an outcome is unconfirmed, inspect get_ticket_integration_import_receipt before retrying. It implicitly requires a prior preview but does not explicitly state 'call preview_ticket_integration_import first' or other exclusions.

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