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

Annotations declare this is a non-readonly, non-idempotent, open-world mutation but say nothing about cost. The description adds genuinely consequential behavior: joining a paid room deducts an entry fee from the caller's test USDC, and max_fee_usdc acts as a spend guard. It stops short of saying whether rejoining charges again, whether the fee is refundable, or what happens when the fee is refused.

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?

Two short sentences with no filler, and the core action leads. Slightly terse given the financial consequence, but every sentence earns its place.

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?

There is no output schema, so the description needn't explain return values, but for a non-idempotent paid mutation it omits important context: what happens if already a member, whether the fee is charged once or per join, and what failure looks like when max_fee_usdc blocks the join. Adequate for a happy-path call, incomplete around edge cases.

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 100%, so the baseline is 3. The description goes slightly beyond the schema by identifying the funding source for the fee (test USDC) and framing max_fee_usdc as a spend cap rather than merely a threshold, which clarifies the currency semantics the schema leaves implicit.

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 a specific verb and resource ("Join a room") and immediately clarifies the payment dimension of that action. It is clearly distinguishable from siblings like room_leave or rooms_list by the verb alone, though it never names those alternatives explicitly.

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 real guidance for one scenario: paid rooms charge an entry fee, so set max_fee_usdc to cap it. Beyond that, there is no stated prerequisite (membership, auth, invite), no guidance on free vs paid rooms, and no exclusions or named alternatives.

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