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

Annotations already declare this is not read-only, not idempotent, and not destructive, so the description's main added value is the visibility disclosure — 'for everyone in the room to see' signals a public broadcast effect. It still omits whether the action is reversible, how long the state persists, or what 'the room' means for the caller.

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?

A single well-formed sentence with the action front-loaded and the consequence appended. It is tightly written, though the brevity edges into under-specification rather than pure economy.

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?

With no output schema and only safety-oriented annotations, the description should carry more: what changes in the room, who observes it, and whether a prior seated state is required. The visibility hint helps but leaves the agent guessing about the action's effect.

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 100% and all three parameters (key, shadow, idempotency_key) are authentication/idempotency mechanics fully explained in the schema. The description adds nothing about them, which is appropriate — baseline 3 applies since no functional parameters need elaboration.

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 gives a concrete verb (stand up) and a scope (everyone in the room can see), which hints at a public, visible action. However, it never establishes the domain — whether this is a physical-world gesture relayed through the app or a virtual room state — leaving it hard to distinguish from siblings like 'stand', 'sit_down', or 'act'.

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?

No indication of when to use this versus 'stand' or 'sit_down', no prerequisites (must you be seated first?), and no exclusions. The agent must infer usage entirely from the name and the sibling list.

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