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

No annotations are provided. The description adds minimal behavioral context beyond the name ('list' implies read-only), but fails to disclose side effects, permissions, rate limits, or return structure. For a tool with no annotation coverage, this is insufficient.

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?

A single sentence of 13 words is highly concise and front-loaded. Every word adds value; no wasted space.

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?

With one optional parameter, no output schema, and no annotations, the description leaves significant gaps. It does not explain what capabilities are, what fields are returned, or pagination. Compared to siblings like 'get_capability', more context is needed.

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?

Schema description coverage is 0%, so the description must compensate. It states 'optionally by category' but does not specify valid values, format, or behavior for the 'category' parameter. This adds some context but is vague.

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 the verb 'List' and the resource 'capabilities the open CHP adapter ecosystem declares'. It distinguishes from siblings like 'get_capability' (singular) and 'list_adapters' (different resource type).

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 mentions optional category filtering but provides no explicit guidance on when to use this tool versus alternatives like 'get_capability' or 'search'. No when-not-to-use or contextual hints.

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