razz_browse_rooms

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

With no annotations provided, the description carries full disclosure burden. It adds minimal behavioral context beyond the operation type, only noting access control ('rooms the agent can access'). It omits pagination behavior, rate limits, whether results are cached, or what constitutes a 'room' entity.

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 sentences with zero redundancy. The first states the action, the second clarifies the access scope. Every word earns its place without repetition of the tool name or schema details.

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?

Adequate for a simple listing tool with optional parameters. However, lacking an output schema, the description should ideally specify what room attributes are returned (IDs, names, participant counts). As written, it provides minimal viable context.

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?

Input schema has 100% description coverage with clear parameter documentation. The description adds no parameter-specific guidance, but with complete schema coverage, this meets the baseline expectation.

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 uses a specific verb ('Browse') and resource ('rooms'), clearly indicating a listing operation. However, it fails to differentiate from sibling 'razz_get_rooms' or clarify whether this includes game-specific rooms (crash/hexwar) or excludes them.

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 is provided on when to use this tool versus alternatives like 'razz_get_rooms' or the specific game room getters (razz_get_crash_rooms, razz_get_hexwar_rooms). No prerequisites or exclusion criteria are stated.

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