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

The description adds useful behavioral detail beyond the annotations: you are physically walked to the front of the stage, and your say is directed to the event's conversation. It also notes the special game-related behavior. Annotations already cover safety/idempotence, so the description supplements rather than repeats them.

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?

The description is two tight sentences with no filler. The core action is front-loaded, and the second sentence adds necessary behavioral nuance about being walked to the stage and how say behaves. Every clause 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?

For a simple action tool with complete parameter schema and informative annotations, the description provides enough context for correct invocation. It explains the immediate in-world effect and conversation routing. A return value or error condition is not described, but the absence of an output schema makes that less critical.

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?

Both parameters have full descriptions in the input schema, including examples and context for room and eventId. The tool description does not need to add parameter details. It does mention 'say' conceptually, which helps clarify the event's conversation, but the schema is already sufficient.

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 clearly states the tool's purpose: 'Join the audience of an event' and clarifies the special behavior for games. It is a specific verb+resource pairing. However, it does not explicitly differentiate itself from nearby siblings like join_conversation or host_event beyond the context of being an audience member.

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?

The description gives clear context for when to use the tool: when the user wants to attend an event and have their say routed to the event's conversation. It does not explicitly name alternatives or provide exclusion criteria, but the intended usage is strongly implied.

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