compute-ledger__get_inventory

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

The description notes the record is 'immutable', which is a key behavioral trait. However, it does not disclose what happens for invalid IDs, required permissions, or rate limits. With no annotations, it carries the full burden but provides minimal behavioral detail.

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?

The description is a single sentence with no redundancy. It front-loads the namespace and immediately states the purpose. Every word earns its place.

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?

For a simple fetch operation with one parameter and no output schema, the description is mostly complete. It states the return is a single immutable record, though it does not detail error scenarios or record structure.

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 0%, so the description must compensate. It mentions 'by inventory_id' but does not explain the format or source of the ID. This adds some meaning but is minimal given the single parameter.

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 clearly states the action 'Fetch', the resource 'immutable inventory record', and the identifier 'by inventory_id'. It differentiates from sibling tools like 'list_inventories' which lists all records.

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 guidance on when to use this tool vs. alternatives (e.g., list_inventories). The description only implies usage when you have an inventory_id, but lacks explicit when/ when-not instructions.

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