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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds the scope of what is described (valid filters, groupings, etc.), which is useful but does not disclose additional behavioral traits such as return format or whether it lists all possible values. The bar is lowered due to annotations, and this meets it without exceeding.

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, concise sentence that is front-loaded with the verb and resource. Every word earns its place; there is no redundancy or 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 describe tool with no parameters, the description fully covers what it does and what content it returns. The output schema exists, so return values need not be explained. Combined with annotations and the sibling query tool context, the description is complete and unambiguous.

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?

There are no parameters (0 params), so the baseline is 4. The description adds meaning by explaining the tool's output scope, but no parameter semantics are needed. The schema coverage is vacuously 100%.

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 states a specific verb ('Describe') and resource ('power.price_ercot'), and enumerates the exact types of information covered (filters, groupings, metrics, detail fields, citation fields). This clearly distinguishes it from other describe tools for different datasets and from the corresponding query tool.

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 its usage context: before constructing queries, users need to know valid filters, groupings, etc. There is no explicit 'use when' statement or alternative exclusion, but the context is clear given the sibling query tool for the same dataset. Not explicit enough for a 5.

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