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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the calculation intent but does not mention whether the operation is read-only, has side effects, uses specific emission factor sources, or what the output structure is. This lack of context is a notable gap.

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?

One sentence that is front-loaded with the action and object, with no filler. It is appropriately concise for a simple calculation tool.

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 11 parameters and no output schema, the description could explain which codes are mutually exclusive or how the spend-based method works. However, the schema covers parameter descriptions, and the tool's scope is simple enough that the minimal description may suffice, though additional context about selecting classification codes would improve completeness.

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 coverage is 100%, so all parameters have descriptions in the schema. The description adds no additional meaning beyond the schema, just the 'spend-based' hint. 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?

The description uses a specific verb 'Calculate', resource 'CO2e emissions', and scope 'business transaction (spend-based)'. The parenthetical 'spend-based' distinguishes it from sibling tools like calculate_emissions_activity, flight, and freight, making the purpose unambiguous.

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 term 'spend-based' implies the tool is for transaction spend data, but there is no explicit guidance on when to choose it over alternatives such as calculate_emissions_activity. No exclusions or named alternatives are provided.

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