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

The description asserts 'Nothing is read or changed,' but annotations declare readOnlyHint=false and destructiveHint=true, i.e. a potentially destructive write. That is a direct conflict about the tool's side-effect profile, and an agent cannot tell which source to trust. The stub disclosure is valuable, but it is stated in a way that contradicts the structured safety metadata.

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?

Four short sentences, front-loaded with the decisive fact that no support-desk API exists. Minimal waste, though 'MCP will not pretend a ticket was filed' and 'Nothing is read or changed' partly restate the same point.

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 7-parameter tool with zero schema coverage and annotations claiming destructive writes, the description is too thin: it does not say what an agent should do instead, whether the params are validated or discarded, or what (if anything) the call returns. It resolves the 'is this implemented?' question but little else.

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?

Seven parameters with 0% schema description coverage and the description says nothing about any of them. Critically, it does not say whether these inputs are ignored, validated, or rejected by the unimplemented stub, and opaque fields like acknowledgedAmountUsd and idempotencyKey go entirely unexplained.

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 never states what the tool does beyond the title; its content is a negative claim ('There is no support-desk API in this app... This tool is not yet supported'). It does make clear the tool is a non-functional stub, which is the most important fact, but an agent must infer the intended purpose (filing a support ticket) from the name alone.

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?

Effectively answers 'when should I use this?' with 'never — it is not supported', which is unambiguous routing guidance and prevents wasted invocations. It stops short of naming a fallback (e.g. get_support_ticket for reading existing tickets), so the agent is left with no alternative to route to.

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