list_agents

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

With no annotations, the description carries the full burden of disclosing behavior. The verb 'list' implies a read-only operation, but the description does not state whether authentication is required, whether the roster is global, or what happens if there are no agents. No side effects or safety characteristics are disclosed beyond the minimal verb.

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 a single, concise sentence that is front-loaded with the core action. It contains no redundant words or filler, making it highly efficient.

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?

The tool is simple (one optional parameter) but lacks annotations and an output schema. The description does not specify return values, the meaning of 'roster,' or any behavioral caveats. This leaves important gaps for an agent attempting to invoke the tool correctly.

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?

The schema has 0% description coverage and the only parameter, since_minutes, is not explained in the description. The parameter name is self-explanatory (a time window), but the description does not confirm that it filters results by recency, nor does it clarify the default behavior when omitted.

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 states the tool lists agents, with the scope of 'seen recently on the roster.' This clearly identifies the action and resource, and it distinguishes from sibling tools like list_chats or list_rooms. However, 'roster' and 'recently' are not fully defined, leaving some ambiguity.

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. The description does not mention any prerequisites, typical use cases, or exclusions, and sibling tools like get_status or register_agent are not referenced.

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