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

'Nothing is read or changed' is consistent with readOnlyHint=true and destructiveHint=false, and usefully discloses that the call is a no-op rather than a real retrieval. It stops short of stating what actually happens on invocation (thrown error vs. empty payload) and does not reconcile the oddly mutation-flavoured parameters (confirm, idempotencyKey, acknowledgedAmountUsd) with a read-only stub.

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?

Three short sentences with the unavailability stated up front, which is the right ordering for a dead tool. Nothing is padded, though the third sentence repeats the read/write message already inherent in 'not yet supported'.

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 stub with no output schema and no annotations covering error behaviour, the description should say what a caller experiences when invoking it and what to use instead. Neither is present, leaving an agent unable to decide this over send_support_ticket or other ticket-adjacent tools.

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% across five parameters, so the description carries the full explanatory burden and adds nothing. If the tool is non-functional the parameters are arguably moot, but acknowledgedAmountUsd and idempotencyKey are genuinely confusing and get no clarification.

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 states plainly that no support-desk API exists here and the tool is unsupported, which does let an agent tell it apart from functional readers like get_receipt. However, it defines the tool by negation rather than saying what a call would actually yield (an error, an empty result, or nothing at all), so the operational purpose remains ambiguous.

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?

'This tool is not yet supported' implies the agent should avoid it, but no explicit directive is given and no alternative is named. The sibling list contains send_support_ticket, which is the obvious substitute for anything ticket-related, and the description never routes the agent there.

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