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

The description asserts 'Nothing is read or changed', while annotations declare readOnlyHint=false, destructiveHint=true, openWorldHint=true and idempotentHint=false. These are directly at odds: an agent trusting the annotations would treat this as a destructive open-world write, and one trusting the text would treat it as a no-op.

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 blocking constraint and ending with the no-side-effect claim. Nothing is padded, though the sentences are terse enough to read as fragments.

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 6-parameter, no-output-schema tool the description explains nothing about the parameters, and the one behavioral claim it does make conflicts with the annotations. A 'do not call' stub can be brief, but leaving the safety profile contradictory is not complete.

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?

Six parameters with 0% schema description coverage, and the description mentions none of them. Fields like confirm, idempotencyKey and acknowledgedAmountUsd are especially opaque and get no explanation from either source.

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 names the operation (joining a meeting room) and explains the underlying requirement (a mediasoup WebRTC client), then states plainly that the tool is not yet supported. An agent can tell what the tool would do and that it is currently unavailable, though it never spells out the intended effect in the positive sense.

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 a strong negative usage signal: MCP cannot open the media path or start billing, so the tool should not be invoked. No alternative sibling is named (e.g. create_meeting_room or a web client), which keeps it short of a 5.

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