get_gas_index

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

Annotations already indicate readOnlyHint=true, but the description adds valuable behavioral context: returns composite score, pipeline counts, operators, verdict, and notes CC-BY-4.0 attribution requirement. No contradictions 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?

Packed with information but every sentence earns its place. Front-loaded with the tool's purpose, followed by parameter explanation and usage example. No redundant or vague phrasing.

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 no output schema, the description lists all returned fields (DCGI, gas_access_score, gas_cost_score, pipelines, operators, verdict) and the 0-100 scale. Attribution requirement is noted. Completes the picture for an AI agent to use the tool effectively.

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?

Despite 0% schema coverage, the description fully explains both parameters: 'state' is a 2-letter code (with example 'TX'), and 'limit' is an optional integer for national ranking. This adds meaning far beyond the bare 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?

Clearly states it returns DCGI per US state, distinguishing between single-state breakdown and national ranking. The verb 'get' combined with 'gas_index' precisely conveys the resource. Sibling tools are on different topics (grid, energy prices, etc.), so no confusion.

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?

Explicitly instructs to pass 'state' for a single state's full breakdown (with specific fields) and to omit 'state' for a national ranking with optional 'limit'. Also advises to quote the score and verdict with attribution, guiding the agent on how to present results.

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