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

No annotations are provided, so the description carries the full burden, and it does disclose a lot: the emissions source/version, that biomass CO2 is reported separately as biogenic, and that it returns per-item and total CO2e. It omits operational details like the 50-item cap enforced by the schema and any error behavior, but for a read-only computation tool this is close to complete.

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?

Front-loads the core purpose and scope, then adds unit guidance, the biogenic caveat, the stationary-vs-mobile limitation, and the sibling pairing. It is dense but every sentence contributes; a reader gets the essential constraints in the first two sentences.

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 still explains the return shape (per-item and total CO2e, separate biogenic CO2). Combined with the scope, source, and unit coverage, an agent has everything needed to invoke it correctly alongside calculate_emissions.

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?

Top-level schema description coverage is 0%, but the description compensates by mapping acceptable units to fuel types (natural gas in therms/ccf/mcf/scf, propane/diesel/heating oil in gallons, coal in short tons) and showing the fuel/quantity/unit item shape via a concrete example. The nested property descriptions exist in the schema, so the description reinforces rather than duplicates.

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 (calculate Scope 1 stationary-combustion emissions) and names the exact gas species and data source (EPA GHG Emission Factors Hub 2025). It explicitly contrasts itself with the sibling calculate_emissions, which handles Scope 2 electricity, so an agent can distinguish the two without opening either schema.

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?

Gives explicit routing: 'Pair with calculate_emissions for a facility's electricity (Scope 2)' names the alternative and the condition that selects it. It also states the exclusion clearly ('Stationary sources only') and explains why vehicle fuel is out of scope (different CH4/N2O factors), which is when-not guidance.

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