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

The description adds meaningful mode behavior beyond the annotations: with no reference it returns the user's support requests and statuses, while a reference returns one request in full with conversation from both sides. 'Reads only' repeats readOnlyHint=true rather than adding new safety context, and no pagination or output shape detail is given, but the dual-mode behavior is well disclosed.

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 compact sentences front-load the two modes and then the use case. There is no filler, and every clause contributes to selecting or invoking the tool.

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 one-optional-parameter read-only tool with rich annotations and no output schema, the description covers scope, modes, and usage well. It could be slightly more complete by clarifying that the list is scoped to the authenticated user's own requests and what status information is included, but nothing essential 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 coverage is 100%, and the schema already explains that a reference like RL-7Q4M2X reads one request in full while omitting it returns the list. The description reinforces that mapping but adds no parameter syntax, format, or edge-case detail beyond the schema, so 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?

The description clearly states the resource: the user's own support requests, either as a status list or a single full request with both sides' messages. It does not explicitly name sibling tools like open_support_request or reply_to_support, but the read-only framing helps distinguish it from those actions.

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 clear usage context: use when the user asks whether support answered or wants the answer read back. It does not explicitly state when not to use it or name the alternative write-oriented siblings, but the guidance is concrete enough for selection.

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