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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description does not need to repeat the read-only nature. However, it adds no additional context such as what happens on failure, how status is reported, or any side effects. It is consistent with annotations but provides minimal extra 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?

The description is a single short sentence, which is concise, but it is under-specified for the tool's complexity. It is not a matter of wasting words; it simply lacks necessary detail, so it is not appropriately sized.

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?

Given that the tool has a nested object parameter with no documentation and no usage context, the description is incomplete. It should explain the request structure, what the output contains, and how this fits into the broader support workflow.

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?

The only parameter 'request' is an object with zero schema description coverage, and the description does not mention it at all. An agent has no information on what fields or structure the request object requires, making it impossible to invoke correctly.

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 clear verb 'Read' and a resource 'support report status', but 'support report' is vague and does not distinguish from sibling tools like support_report_error or tasks_get_status. It lacks specificity about what constitutes a support report or what status means in this context.

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?

No guidance on when to use this tool versus alternatives. It does not mention any prerequisites, contexts, or exclusions. An agent cannot determine whether this is the right tool for a given situation.

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