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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description earns credit for adding non-obvious context: results are bounded/retained rather than live, and the response is metadata only with no encrypted payloads, credentials, or fresh provider state. The intent-ID warning about not resending is a genuinely useful behavioral constraint.

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?

Four dense sentences, all load-bearing, front-loaded with the core action and scope. No filler or restatement of the title.

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 exists, and the description does cover the return profile at a high level (metadata only, no payloads/credentials) and pagination continuation, but it leaves limit defaults, provider filtering behavior, and ownership semantics unexplained for a four-parameter 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?

Schema description coverage is 0% across four parameters, so the description carries the full burden, yet it only alludes to pagination via next_before_id/has_more (which are response fields, not the before_id parameter) and says nothing about limit, the jira/linear provider filter, or the meaning of ticket_id ownership. This is insufficient compensation for a completely 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: reading retained export and transition outcomes for an owned ticket, with a bounded scope. It is distinguishable from write-side siblings like export_ticket_to_provider or reconcile_ticket_provider_effect, though it never names the closest sibling (list_ticket_provider_observations) to sharpen the boundary.

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 concrete prerequisites (requires tickets:read or tickets:write), pagination instructions (follow next_before_id while has_more), and a caution against treating historical outcomes as permission to resend. It lacks explicit when-to-use-this-vs-alternative routing, which keeps it from a 5.

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