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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds genuinely new behavioral context: the tool switches modes based on whether a ticket reference is supplied, and that supplying one returns the full conversation rather than just metadata. It still omits pagination and result ordering, but the mode-switch disclosure is real added value.

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?

Two short sentences, front-loaded with the resource and followed immediately by the parameter behavior. There is no filler or redundancy.

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 annotations covering safety and a simple single-optional-parameter schema, the description is minimally adequate. It never states what the listing (no-parameter) mode returns, whether there is pagination or a result cap, so the description is slightly thin for a list tool with no output schema.

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% and the schema already documents the 'ticket' parameter with an example ('TK-1A2B3C'). The description goes beyond the schema by explaining the consequence of passing it — reading that ticket's full conversation — which the schema alone does not convey.

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 names the specific resource (the user's FirmLedger support tickets) and implies the list/read behavior, with the name and title supplying the verb. It is clear enough to distinguish from create_support_ticket, but there is no explicit differentiation from other sibling read tools.

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 gives one concrete usage instruction ('Pass a ticket reference to read that ticket's full conversation'), which implies dual-mode behavior (no param = list, param = read one). However, there is no explicit guidance on when to use this versus alternatives, nor any prerequisites or exclusions.

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