List agents

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

No annotations are provided, but for a read-only list operation the description covers the core behavior adequately. It doesn't disclose whether this is read-only, whether it reflects live or cached state, ordering, or pagination, but a simple list operation has limited behavioral surface to disclose. Acceptable given the simple nature.

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?

One sentence, zero waste. Front-loaded with the verb 'List' confirming the scope. Exactly as concise as it should be for a simple no-parameter list operation.

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 zero-parameter listing tool with no output schema, the description is largely sufficient. No prerequisite setup, auth, or state dependencies are mentioned, which could matter in a mesh context, but the primary function is fully conveyed. Slight gap on return format but acceptable for an agent listing tool.

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 there is nothing to document beyond the description itself. Schema coverage is 100% trivially, and the description accurately conveys what the tool returns (registered agents in the mesh). Baseline 4 for a zero-parameter tool is appropriate.

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?

Clear verb+resource: 'List every agent registered in the mesh.' Distinguishes from siblings like register/send/broadcast which are mutation/communication tools. Could be slightly sharper about why it differs from tmux_attach_info, which likely also lists agents/attachments, but the verb+scope is clear.

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 explicit when-to-use or alternatives guidance. The context signals show 0 parameters and sibling tools for discovery vs registration vs messaging. The description implies it's for discovering registered agents but doesn't state when to prefer it over tmux_attach_info or contrast with registration.

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