list_processes

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

With no annotations provided, the description must disclose behavioral traits. It describes the return value (simple list with specific fields) but does not explicitly state that it is a read-only operation or any side effects. The behavior is typical for a list tool but lacks full transparency.

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 two sentences long, with the first sentence front-loading the primary function: 'List all running and completed AI agent processes.' The second sentence adds return field details. No unnecessary 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?

Given the tool has no parameters, no annotations, and no output schema, the description provides the essential return fields (PID, agent type, status). It does not mention ordering, error conditions, or performance, but for a simple list operation this is nearly complete.

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 has no parameters, so the description has no parameters to explain. Baseline for zero parameters is 4, and the description does not add any parameter information, which 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 uses the verb 'List' and the resource 'processes', clearly indicating it returns a list of all running and completed AI agent processes. It includes the specific fields (PID, agent type, status) that will be in the output, distinguishing it from siblings like kill_process or get_result which have different purposes.

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 states it lists 'all running and completed' processes, implying use when you need an overview. However, it offers no explicit guidance on when to use this tool versus alternatives like peek, get_result, or wait, nor does it mention any prerequisites or exclusions.

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