Add item to acquisition

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

Beyond the sparse annotation (only destructiveHint: false), the description adds that the action 'executes directly' and the acquisition remains uncommitted, which are important behavioral traits. The explicit 'Write' label clarifies that this is a mutating operation. However, it does not disclose validation rules, error cases, or idempotency, so it is not fully transparent.

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 short sentences that lead with the purpose and follow with execution context. The trailing 'Write' is optional but does not waste space. Every sentence carries meaning, making it well-structured and easy to scan.

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?

A 21-parameter write operation with no output schema and minimal annotations requires more contextual guidance. The description covers the core intent but omits many operational details: behavior when acquisition is committed, duplicate handling, or which optional fields matter for specific firearm types. The schema partially compensates, but the overall package is under-specified for the tool's complexity.

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?

With 21 parameters and only 48% schema description coverage, the description should compensate by explaining parameter roles, but it adds nothing beyond the domain hint 'firearm'. The schema's partial descriptions are the only source of parameter guidance, and the description does not help disambiguate optional fields or their relationships.

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 'Add' and a clear resource 'a single firearm to a pending acquisition', which distinguishes it from sibling tools like add_disposition_items (disposition vs acquisition) and create_pending_acquisition (which creates the acquisition rather than adding items). The scope 'single firearm' adds useful precision.

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 phrase 'pending acquisition' and 'still uncommitted' implies when to use the tool, but it does not explicitly mention alternatives or exclusions (e.g., for modifying an existing item use update_acquisition_item). Usage guidance is present but only implicitly, requiring the agent to infer from sibling names and context.

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