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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description adds real value beyond them: the exact return content (ticket IDs and count, never imported content), the semantic caveat about a false 'found', the guarantee that no provider call or retry is triggered, and the required scopes integrations:read and tickets:read.

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 dense sentences, front-loaded with the verb and scope, then the payload restriction, then the caveat and permission requirement. No filler and nothing repeated from the schema or annotations.

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?

There is no output schema, and the description compensates by describing the return content and the found=false semantics, plus the auth scopes needed. For a two-parameter read tool with full annotation coverage, everything needed to call it correctly is present.

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 the parameter meaning. It clarifies that request_id must be one exact request and implies the provider set (GitHub, GitLab, Asana), but it does not state the UUID format the schema enforces or where an agent obtains a valid request_id, leaving a meaningful gap.

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?

Specific verb+resource+scope: it reads a retained provider import receipt for one exact request_id. It enumerates the three supported providers and explicitly says the payload is created ticket IDs and count only, which cleanly separates it from sibling effect/status tools. An agent can pick this over list_ticket_integration_effects or export_ticket_to_provider without opening a 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?

It scopes usage to a single exact request_id and warns that 'found false does not prove an import failed' plus 'No provider request or retry', which tells the agent this is a passive lookup rather than a recovery action. It never names an alternative tool for the retry/re-check case, so guidance is clear but not fully routed.

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