compute-ledger__get_inventory

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

No annotations provided; description only hints at immutability. Lacks disclosure on authentication, error handling, side effects, or post-conditions.

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, but includes redundant prefix '[compute-ledger — compute-is-carbon energy/carbon ledger]' that adds no value. Core message is clear but could be leaner.

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?

Tool is simple, but with no output schema and low schema coverage, description fails to cover return values, error cases, or behavior when ID is not found.

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 0%; description merely mentions 'by inventory_id' without format, constraints, or examples. Compensation is minimal.

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 verb (Fetch), resource (inventory record), and identifier (by inventory_id), distinguishing from siblings like list_inventories. The term 'immutable' adds specificity.

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 guidance on when to use this versus other tools like list_inventories or verify_inventory_chain. No prerequisites or alternatives mentioned.

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