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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds meaningful context beyond them: tickets:read permission, archived-ticket readability, truncation reporting in history windows, and exact canonical JSON output without raw evidence payloads.

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 and dense with useful scoping information. The four sentences each contribute, though the long noun phrase describing returned metadata is somewhat packed.

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 read-only, no-output-schema tool, the description sufficiently covers purpose, permissions, archived behavior, truncation, output nature, and the main export alternative. It does not detail the semantics of each returned metadata category, but no major invocation gap remains.

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 adds that the ticket must be owned and that archived tickets remain readable, which clarifies ticket_id constraints, but it does not explain format or other selection details beyond the schema's UUID pattern.

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 read of an owned ticket's audited readiness, dependencies, scenario validation metadata, and completion history. It distinguishes itself from ticket_authority_export for retained evidence, though it does not explicitly contrast with other ticket read siblings like ticket_get or ticket_readiness.

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 context: archived tickets remain readable, history truncation is reported, and ticket_authority_export should be used for all retained evidence. It does not fully explain when to choose this over other ticket-read tools, but the main alternative is named.

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