get_grid_scoreboard

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

Annotations already indicate readOnlyHint=true. The description adds behavioral context such as 'live', 'ranked side-by-side', 'renewable share %', and source transparency (EIA, Elexon, ENTSO-E, AEMO). No contradiction with annotations, and it enriches the agent's understanding of what happens when called.

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 quite long and includes many details about regions and sources. While informative, it could be more concise. However, it front-loads the core purpose and is structured with clear sections (regions, metrics, usage hint).

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?

There is no output schema, but the description specifies the kind of data returned (rankings, percentages, MW, demand) and source attribution. For a simple listing tool with no parameters and no nested objects, this covers most necessary context, though format specifics are omitted.

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 baseline is 4. The description explains what the tool does without needing parameters, effectively conveying its semantic meaning.

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 the tool provides a live global grid scoreboard with specific metrics (renewable share, gas share, fuel mix, demand) across many geographic regions. It distinguishes itself from sibling tools 'compare_isos' (pairwise) and 'get_grid_data' (single ISO), making its purpose very clear.

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 explicitly says 'One call answers which grid worldwide is greenest...' and contrasts with siblings. It also mentions attribution requirements. However, it does not provide explicit 'when not to use' guidance beyond referencing alternatives, which is adequate but not exhaustive.

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