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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds value by specifying the categories of information returned (filters, groupings, metrics, etc.), which clarifies the tool's output nature beyond the generic 'describe' label. There is no contradiction with annotations.

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 concise sentence that front-loads the verb and enumerates the metadata categories. Every word contributes to understanding the tool's purpose, with no redundant or extraneous content.

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's deterministic metadata-retrieval nature, the presence of an output schema, and comprehensive annotations, the description fully communicates the tool's role. It does not need to explain return formats since the output schema covers that. The description is complete for an agent to select and invoke the tool correctly.

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 tool has zero parameters, so the input schema provides no parameter details. Per the rubric, baseline is 4. The description does not add parameter-specific information, but that is unnecessary given the absence of parameters.

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 tool's function: to describe valid filters, groupings, metrics, detail fields, and citation fields for the resource power.demand_rollup. It uses a specific verb ('describe') and identifies the exact resource, distinguishing it from sibling tools like describe_power_demand_v1.

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 conveys that the tool provides metadata about the rollup endpoint, which implicitly indicates when to use it (e.g., before querying power.demand_rollup). However, it does not explicitly state usage conditions or contrast with alternative tools, leaving the guidance somewhat implied rather than direct.

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