list_claude_agents

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

No annotations are provided, so the description carries the behavioral burden. It discloses that output is compact summaries, not full reports, and that this is not the normal path. However, it does not describe what a summary contains (e.g., whether IDs are included), ordering, limits, or the read-only nature explicitly.

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 short sentences with no filler. The recovery-only purpose is front-loaded, and the routing guidance to wait_claude_agents earns its place.

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 and the usage context is clear, but there is no output schema, so the description should explain what the returned 'summaries' actually contain—especially whether agent IDs are present for recovery. Without that, an agent may not know how to use the result with wait_claude_agents.

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 tool has zero parameters and the schema is empty with 100% coverage, so the baseline score of 4 applies. There is no parameter documentation burden on the description.

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 identifies the resource ('claude agents') and the key distinction: it returns 'compact recent agent summaries, without full reports.' It does not explicitly use the verb 'list,' but the name plus the noun phrase make the operation clear, and it distinguishes itself from the normal wait/spawn flow.

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?

Explicitly states this is 'recovery only' and gives the normal alternative: use the ID returned by spawn directly with wait_claude_agents. This tells the agent exactly when to choose this tool versus the preferred path.

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