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

The claim 'Nothing is read or changed' is consistent with readOnlyHint=true and destructiveHint=false and adds genuinely useful information beyond the annotations: the tool is non-functional and has no side effects. It does not explain why the schema contains confirm, idempotencyKey, and acknowledgedAmountUsd, which could mislead an agent into thinking a charge is involved.

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 most decisive fact (not supported) placed early, and no filler. Slight deduction for the somewhat indirect opening clause before delivering the actionable 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 deliberately unsupported stub, the description supplies the one thing an agent needs: do not call this. Given no output schema and no required parameters, that is largely sufficient, though the unexplained billing-flavored parameters leave a residual ambiguity worth addressing.

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, and the description explains none of them. In particular, acknowledgedAmountUsd and confirm strongly imply a paid, confirming mutation that an agent would need context on; the absence of any explanation leaves those semantics entirely opaque.

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 identifies the resource and scope ('AI chat recaps ... for organization sessions') and, crucially, states the tool is not supported, so an agent immediately knows this is a no-op stub. It falls short of a full 5 because it never contrasts itself with the consumer-facing chat siblings (list_my_chats, start_chat) that would be the actual correct routes.

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 an explicit when-not-to-use signal ('not a consumer-thread tool', 'not yet supported'), which is the most important routing guidance for this entry. It does not name the alternative tool an agent should call instead, which is why it is not a 5.

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