speechwire_list_rooms

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

No annotations provided. Description includes return value structure but doesn't disclose behavioral traits like read-only nature, rate limits, or prerequisites. With no annotations, more detail expected. However, the output schema exists and description covers the key fields.

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 clear lines: purpose statement and Returns section. No fluff, efficiently structured.

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?

Complete for a simple list-all tool. Output schema exists and description outlines return fields. No obvious gaps given no parameters.

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?

Tool has 0 parameters, so baseline is 4. No parameter description needed.

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?

Description clearly states 'List all rooms configured for the tournament' with specific verb and resource. Distinguishes from siblings like speechwire_get_room_usage which focus on usage rather than listing.

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 guidance on when to use this tool vs alternatives (e.g., speechwire_get_room_counts for counts, speechwire_get_room_usage for usage). No exclusions or context provided.

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