search_rooms

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

No annotations are provided; the description only states 'Search or list' suggesting read-only behavior, but does not disclose any other traits like authentication, rate limits, or whether it modifies state. Minimal transparency.

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 concise sentences without unnecessary words. First sentence states purpose, second adds practical guidance. Could be more structured (e.g., listing params) but efficient overall.

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?

Given the lack of output schema and annotations, the description is too minimal. It does not explain the return format beyond 'room_id', search behavior (e.g., query semantics), or parameter defaults, leaving the agent underinformed.

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 0%; the description adds no information about the three parameters (type, limit, query). The schema itself provides defaults and enums, but the description fails to explain their meaning or usage.

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 searches/lists contacts, groups, and channels, and specifies the returned room_id is used with message tools. It distinguishes from sibling tools like list_channel_posts or send_message.

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 implies usage via 'Use returned room_id with message tools' but does not explicitly state when to use this tool over alternatives, nor does it provide exclusions or when-not-to-use guidance.

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