agent_list

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

Describes read-only nature with no side effects, return format for success and error cases, and parameter behavior. No contradictions; lacks mention of auth or rate limits but acceptable for a simple list tool.

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?

Three concise sentences with front-loaded purpose. Every sentence adds value with no wasted words.

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?

Comprehensive for a simple list tool: covers purpose, usage, return format, parameter details, and sibling tool interaction. Adequate despite lack of output schema.

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?

Adds value beyond schema by listing exact allowed values for status_filter and explaining that omitting it returns all statuses. Schema coverage is 100% but description provides clearer semantics.

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 'List all agents registered with the orchestrator and their current status' with a specific verb and resource. It distinguishes from sibling tools like agent_spawn and agent_stop by indicating it is a read-only list operation.

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?

Explicit guidance to 'Call before agent_spawn or agent_stop to confirm the target agent exists and has the expected status' provides clear when-to-use context and relates to sibling tools.

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