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

No annotations are provided, so the description carries the full load; it does so reasonably by spelling out the full return payload, the eGRID vintage, and a market-based factor alongside the location-based one. It leaves implicit that this is a read-only, idempotent lookup and says nothing about latency, caching, or coverage gaps for ZIPs that don't map to a subregion.

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, front-loaded with the action and scope, then a return-value inventory that earns its place because no output schema exists. The middle enumeration is long but each item is a distinct, non-redundant output.

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?

With no output schema, the description usefully compensates by listing the return fields, and it covers scope and usage context. It is not fully complete for a lookup in a crowded sibling set — it omits the coordinate-based and batch variants and gives no pagination or coverage caveats — but nothing essential for invoking it is missing.

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 description coverage is 100%, so both the zip pattern and the 2023/2024 edition semantics (including that 2024 is preliminary and not official EPA) are already documented. The description adds no parameter-level detail beyond what the schema provides, so the baseline 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?

States a specific verb and resource — 'Look up EPA eGRID electricity emission factors for a US ZIP code' — and enumerates exactly what comes back (CO2e, CH4, N2O, NOx, SO2, mix, subregion, year, Green-e residual). This clearly separates it from lookup_by_coordinates and lookup_batch, the nearest siblings.

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?

Provides a concrete context — 'Use this for Scope 2 location-based and market-based emissions accounting' — which tells the agent when the tool applies. It never names the alternative (e.g., lookup_by_coordinates when a lat/long is available, or lookup_batch for many ZIPs), so routing between siblings is left to inference.

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