list_agents

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

With no annotations, the description must fully disclose behavioral traits. It merely states 'list', implying a read operation, but does not specify pagination behavior, rate limits, or any potential side effects. The description fails to add meaningful behavioral context beyond the verb itself.

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 sentence, which is concise. However, it lacks structure—no headings, examples, or key information front-loaded. While brevity is valued, it sacrifices completeness.

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 lack of output schema and annotations, the description should provide enough context for correct invocation. It omits details like return format, pagination limits, and whether the list is comprehensive. The description is insufficient for an agent to use the tool confidently.

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 includes two parameters (page, limit) but has 0% description coverage. The tool description does not mention these parameters or their semantics. An agent cannot infer how to use pagination from the description alone, which is critical for a list tool.

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 'List registered AI agents' clearly states a verb ('List') and a resource ('registered AI agents'), making the purpose understandable. However, it does not differentiate from sibling tools like 'lookup_agent' or 'get_agent_uri', which could cause confusion about which tool to use for listing vs. retrieving details.

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 guidance is provided on when to use this tool versus alternatives. There is no mention of pagination, filters, or any context about when listing is appropriate compared to other agent-related tools. The description lacks any usage directives.

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