get_global_carbon_intensity

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

No annotations are provided, so the description carries full burden. It discloses that the tool returns CO2 intensity and power mix, and requires a token. This is sufficient for a read-only tool with no side effects mentioned.

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 concise with two short paragraphs. The first sentence immediately states the purpose, followed by parameter details. No extraneous information.

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?

The description covers the purpose, parameter, and token requirement. However, it does not detail the response structure beyond stating it returns CO2 intensity and power mix. For a simple tool with one parameter, this is mostly adequate.

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 input schema provides only the parameter name 'zone' with no description (0% coverage). The description compensates fully by providing concrete examples and explaining the format, adding significant meaning beyond the schema.

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 it gets CO2 intensity for a global zone, specifying the verb and resource. It differentiates from sibling tools by focusing on global zones rather than specific countries like UK or Germany.

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 mentions the required ELECTRICITY_MAPS_TOKEN, which is a necessary condition. However, it does not explicitly state when to use this tool versus alternatives like get_uk_carbon_intensity or get_global_power_mix, leaving some ambiguity.

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