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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is fully covered elsewhere. The description adds nothing about what the endpoint returns, auth requirements, or scope of the status data, so it earns no credit beyond the structured fields.

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 short but wasteful: the same endpoint string appears twice, and the operation ID plus schema pointer consume the remainder without conveying intent. Brevity here comes from under-specification, not economy.

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 read endpoint with no output schema and an opaque, free-form query object, the description should say what status information is returned and what the query object can carry. Neither is present; the agent must leave the tool and call describe_operation to learn anything.

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 description coverage is 0% and the tool exposes two undocumented parameters, one of which is a free-form nested 'query' object with additionalProperties allowed. The description does not describe either; it only redirects to describe_operation, which is a pointer rather than parameter meaning.

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 is a verbatim restatement of the tool title and name ("GET /api/support/status"), repeated twice, plus an operation ID. It names no resource semantics and does nothing to separate it from siblings such as get_support_status_by_id or get_support_status_uptime, so an agent cannot tell which status endpoint it needs.

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 only actionable guidance is "describe_operation provides native request schemas," which points at a sibling for schema retrieval but never says when to call this tool versus get_support_status_uptime or get_support_status_by_id. There are no conditions, exclusions, or prerequisites.

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