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

Annotations already establish readOnly, idempotent, non-destructive behavior, but the description adds substantial context beyond that: no state changes, acknowledgments, notifications or provider calls; requires tickets:read; total_flagged/truncated disclose partial coverage; and detailed ordering and edge-case rules (e.g., weekends never extend commitments, completion blockers have no age). This is exactly the kind of behavioral disclosure the dimension rewards.

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?

The description is long but front-loaded with purpose and return contents, then proceeds through scope, pagination, filtering, ordering, and safety in a logical order. Every sentence appears to carry operational information, though the density and run-on style keep it from being maximally crisp.

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 complex read tool without an output schema, the description is unusually complete: it explains return fields, pagination, refresh behavior, partial-coverage flags, ordering rules, and authentication scope. It stops short of describing error behavior or explicitly linking to sibling tools for policy or resolution, but nothing critical for correct invocation 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?

With 0% schema description coverage, the description must compensate and largely does: it states limit 1–500 (default 100), offset 0–2147483647 (default 0), and explains that reason filtering happens before the limit, with special handling for missed_due_date. It does not define each enum value individually, but it adds meaningful semantics for the two numeric parameters and the filtering behavior.

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 immediately states a specific verb and resource: 'Read the same ranked Needs attention queue as the browser and REST.' It also enumerates the returned data and scopes the operation to 'Open active owned tickets only,' which distinguishes it from sibling tools like get_ticket_attention_policy or save_ticket_attention_review.

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?

The description gives clear operational context: use limit/offset, continue with next_offset when has_more, refresh at offset 0, and be aware that membership/rank can shift between live pages. It does not explicitly name alternative tools or say when not to use this one, but the usage conditions are otherwise well covered.

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