list_agents

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

With no annotations provided, the description carries the full burden of behavioral disclosure, yet it only says 'Show all agents'. It does not state that this is a read-only operation, describe the return format, or explain what happens if the session does not exist or has no agents. The phrase 'current session' also introduces ambiguity about whether the required sessionId parameter is actually needed.

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, 11-word sentence that front-loads the action and resource without any filler. Every word contributes to meaning.

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 simple list tool with one parameter and no output schema, the description is minimally viable but incomplete. It lacks details about the response structure, the meaning of 'status', and any error cases, leaving clear gaps that an agent would need to infer.

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 input schema already fully documents the single parameter sessionId, so baseline is 3. The description's mention of 'current session' adds no new information about the parameter and could be slightly confusing, but it does not contradict the schema, so a baseline score 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?

The description clearly states a specific verb ('Show') and resource ('all agents'), and specifies the scope ('in the current session') and the included detail ('with their status'). This distinguishes it from sibling tools like get_agent_status, which targets a single agent.

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 a clear use case—listing all agents in a session—but does not explicitly discuss when to use it over alternatives or mention any exclusions. For example, it does not direct users to get_agent_status for single-agent details, so guidance is only implied.

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