get_gas_economics

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

Annotations already indicate read-only and idempotent behavior. Description adds value by detailing the output structure (markets, scenarios) and explaining the calculation context. No contradiction.

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?

Single, front-loaded paragraph with no wasted words. Every sentence adds essential information about purpose, usage, parameters, and outputs.

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?

Despite no output schema, description fully explains return fields including nested scenarios. It also mentions pairing with get_gas_index. Sufficient for an AI agent to understand the tool.

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 covers 100% of parameters. Description adds context beyond schema by explaining where market slugs come from (rank_markets/get_market_dcpi_rank) and providing example slugs. Baseline 3, plus extra context gives 4.

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?

Description clearly states 'Behind-the-meter / gas-fired power ECONOMICS' and specifies the output is for BTM developers comparing against grid PPA. It also distinguishes from sibling tools by naming what not to use it for (get_grid_data, get_gas_index).

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 provides when to use (compare against grid PPA) and when not to use (grid fuel mix, per-state gas suitability), with specific alternative tool names (get_grid_data, get_gas_index).

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