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

Annotations already provide readOnly/idempotent/non-destructive hints, and the description adds substantial behavioral detail beyond them: the tickets:read permission, exclusive before_revision semantics, default limit of 20, persistence of history after ticket lifecycle events, the separation of evidence-changed versus follow-up-due states, and the IANA calendar-day due-date rule. This is rich, non-redundant context.

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 compact, information-dense sentences with no filler. Core purpose is front-loaded, followed by auth, then pagination/lifecycle behavior, then state/date semantics. Every sentence contributes unique value and the total length is appropriate for the complexity.

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 names what is returned (current assessment, latest review, immutable history) and covers tuning, permission, lifecycle, state modeling, and date semantics. For a read-only, idempotent tool with only three simple parameters, nothing material an agent needs to call it correctly is missing.

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 carries the burden. It explains limit semantics (range, default) and before_revision (exclusive cursor). ticket_id is not explicitly described, but its role is obvious from 'Read the owner-private current attention assessment' plus the required field. This is good compensation, though not exhaustive.

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?

The description uses a specific verb ('Read') and names a precise resource: the owner-private attention assessment, latest review, and immutable history. It also explicitly disclaims writes ('No writes or providers'), which helps distinguish this read tool from save_ticket_attention_review and from policy/queue siblings.

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 states a clear precondition (requires tickets:read), explains pagination behavior (limit 1–50, default 20, exclusive before_revision), and notes that history remains readable after ticket closure/archive/deletion. It does not explicitly name alternative sibling tools or state when to choose them, but the scope and 'No writes' statement provide adequate context.

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