compute-ledger__footprint

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

With no annotations, description must convey behavior. It states 'Totals are exact sums of ledger entries' indicating read-only aggregation. However, it does not mention authentication needs, rate limits, or potential side effects.

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 purpose and metrics, no redundancy. Every sentence adds value.

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 1 parameter, no output schema, and no annotations, the description covers the return metrics and data source. Lacks clarity on time scope or ledger context, but is mostly sufficient for a simple aggregation 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 has 0% description coverage for parameters; the description only vaguely mentions 'for an agent' without explaining agent_id format or source. More information is needed for correct usage.

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 it aggregates footprint for an agent, listing specific metrics (J, kWh, gCO2e, cost, mean Landauer efficiency). It distinguishes from sibling tools like list_entries by focusing on sums rather than individual entries.

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?

No explicit when-to-use or when-not-to-use guidance given. The description implies it is for obtaining aggregate footprint data, but does not contrast with alternatives like ghg-ledger__calculate_inventory or compute-ledger__describe_agent.

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