pgiq_grid

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

No annotations provided, so description carries full burden. Does not disclose behavioral traits such as data freshness, read-only nature, idempotency, rate limits, or side effects. Only lists returned metrics.

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?

Two sentences with no wasted words. First sentence enumerates what the tool provides; second states use case. Could be slightly more scannable with bullet points but overall concise.

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 only one parameter and no output schema, the description lists key metrics but not the output structure or format. For complex data like fuel mix and peak stress, more detail would be helpful. Adequate but not thorough.

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% with one parameter 'market' described as 'Market id, e.g. 'quebec'.' The tool description adds no extra information about the parameter beyond the schema, so baseline score of 3 applies.

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?

Clearly states it provides a grid snapshot for one market, listing specific metrics (carbon intensity, price, fuel mix, demand, etc.). Differentiates from siblings by focusing on a single market and listing unique data points.

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?

Implies use for scheduling decisions ('The inputs for carbon- and cost-aware scheduling'), but does not explicitly state when to use this tool versus alternatives like pgiq_best or pgiq_cheapest_window. No when-not guidance.

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