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

readOnlyHint=true already establishes safety, so the bar is lower; the description adds useful context beyond annotations — default sort order, the REST endpoint, the return-shape note about summaries, and the pagination caveat. It does not cover rate-limit nuances beyond what the schema's count description already states.

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 short sentences, front-loaded with purpose and default behavior, with no filler. Every clause carries usable information.

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 14-param read tool with full schema coverage, readOnly annotation, and no output schema, the description covers purpose, default ordering, the unassigned filter trick, and the summary-vs-messages distinction. Only minor gaps remain (e.g., no explicit note on the large result-set guidance beyond the schema's since_created_at hint).

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 coverage is 100%, so every parameter already has documentation; the description only reinforces existing facts (default sort, the "null" unassigned convention) rather than adding new syntax or semantics. Baseline 3 is appropriate.

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+resource ('List and filter tickets') with scope (newest first by default), and explicitly distinguishes itself from enchant_get_ticket by noting results carry only short summaries while messages require the sibling.

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 the alternative for detail retrieval (enchant_get_ticket for messages) and a concrete usage trick (user_ids ["null"] for unassigned), but offers no when-not guidance for listing itself or exclusions relative to other list tools.

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