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

The description says 'Nothing is read or changed', but the annotations declare readOnlyHint=false and destructiveHint=true. These directly conflict, which is an annotation contradiction.

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, direct sentences with no wasted words. The opening sentence about the meeting room service is slightly less useful than leading with '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?

The tool has 6 undocumented parameters, contradictory annotations and no output schema. It does not say what the call returns, such as an error or a stub response.

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 coverage is 0% across 6 parameters, and the description explains none of them. Odd fields like acknowledgedAmountUsd, confirm and idempotencyKey are left 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 says plainly that the tool is unsupported and that recording is handled by the meeting room service. It does not say what the tool would do if it worked, or which sibling or external path an agent should use instead.

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?

Stating that the tool is not yet supported implicitly tells the agent not to use it. It names no alternative, such as a meeting-room tool or a deep link, for accomplishing recording control.

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