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

With no annotations, the description carries the burden of behavioral disclosure. It states that 'Each capability requires a quote before execution' and 'No API key required', which are important behavioral notes. It does not detail return format or error behavior, but for a listing tool, this is sufficient. Cannot score 5 due to lack of error or edge-case handling, but it exceeds a baseline 3.

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 three sentences, each earning its place: the first states the action and output, the second gives usage priority, and the third covers prerequisite and required auth. It is front-loaded with the core purpose. No fluff.

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 one-parameter listing tool with no output schema, the description covers the essential information: what is listed, the optional filter, the prerequisite quote, and no API key. It doesn't explain pagination or exact output structure, but the output fields are mentioned. Given the tool's simplicity, this is nearly complete. The mention of 'quote required' is crucial since all siblings are quote tools.

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 coverage is 100% for the single optional 'domain' parameter. The description says 'Optional filter by scientific domain' and lists examples, which adds value beyond the schema's own description (which also lists examples, but the description reinforces the optional nature and gives more context). Given high coverage, baseline is 3, but the description's explicit mention of filtering and examples elevates it slightly.

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 purpose: 'List all available environmental intelligence capabilities' and specifies what is returned (capability IDs, names, descriptions, domains). It uses a specific verb 'List', identifies the resource 'environmental intelligence capabilities', and provides distinct output fields. This distinguishes it from siblings like get_capability_details and the quote functions.

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?

It explicitly says 'Use this first to see what AOI can do', which is a clear when-to-use instruction. It also implies it's a discovery tool before requesting quotes, and the presence of many sibling quote tools suggests this is the entry point. The description does not explicitly exclude situations, but the 'Use this first' is strong guidance.

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