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

Annotations already cover the safe-read profile, and the description layers on substantial behavioral detail beyond them: it never returns payloads, requires integrations:read and tickets:read, performs no provider request/retry/reconciliation, shows no settlements in v2, and notes that a cancelled effect with attempt_count 1 still blocks and cannot be settled.

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?

Front-loaded with the returned resource, then behavioral and pagination constraints; nearly every sentence carries load. A few clauses (the deploy-owned settlement activation phrasing) are dense, but nothing is wasted.

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?

With no output schema, the description carries the return-value burden and does so: page shape (newest-first, bounded), per-item fields (blocking status, immutable settlement), the absence of payloads, pagination mechanics, and auth scopes. An agent has everything needed to call it correctly.

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?

With 0% schema description coverage the description must compensate, and it does for most parameters: limit gets a default (20) and cap (50) not present in the schema, before_id gains pagination semantics ('use next_before_id while has_more'), and ticket_id is narrowed to 'one owned ticket'. Only provider is left to the enum, so compensation is strong but not total.

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 ('bounded newest-first page of one owned ticket's recorded GitHub, GitLab and Asana write effects') and explicitly positions itself as version 2 of a known sibling. An agent can distinguish it from list_ticket_integration_effects and list_ticket_provider_effects without opening the 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 concrete usage conditions: default 20 / max 50, 'use next_before_id while has_more', and the v2-vs-v3 timing around settlement activation. It stops short of explicitly routing the agent between sibling list tools, so it is clear context rather than full when/when-not guidance.

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