Add items to disposition

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

Annotations only provide destructiveHint: false. The description adds 'Executes directly' and 'Write', which clarify that the operation is an immediate mutation and not read-only. This adds some context beyond annotations but does not disclose error conditions, audit trail behavior, or constraints like the disposition status. Overall, moderate transparency.

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 extremely concise: two sentences with no filler. The first sentence captures the core function, and the second provides behavioral context ('Executes directly' and 'Write'). Every sentence serves a purpose, though 'Write' is somewhat redundant with 'Add'.

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 tool with 3 parameters and no output schema, the description covers the essential purpose and the pending-disposition condition. However, it lacks guidance on how this fits into the overall disposition lifecycle (e.g., must be before commit), or what happens if the disposition is not pending. The schema fills in parameter details, so completeness is adequate but not outstanding.

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%, with descriptions for all three parameters. The description reiterates that items are added 'by GUID' and 'optionally with a price', which aligns with the 'id' and 'price' properties in the schema. It adds little beyond the schema, so baseline 3 is appropriate.

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 a specific action: 'Add inventory items (by GUID, optionally with a price) to a pending disposition.' It specifies the target resource (pending disposition), the input type (GUID), and optional price. This distinguishes it from sibling tools like remove_disposition_items and edit_disposition_item_price.

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 description indicates the context: 'to a pending disposition', which implies it should only be used for pending dispositions. However, it does not explicitly mention when not to use it (e.g., committed/locked dispositions) or suggest alternatives like remove_disposition_items. The guidance is clear but lacks exclusionary details.

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