boundbook_reconcile

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

With no annotations provided, the description carries the full burden. It discloses that apply=false is a read-only dry run and apply=true removes from stock (with confirm requirement). This covers key behavioral traits. No contradictions with annotations (none present).

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 concise (3 sentences) and front-loaded with the purpose. Every sentence adds value, including parameter explanations. No wasted words.

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 the complexity of a reconciliation tool with side effects, the description provides sufficient context for usage. It covers the core logic, parameter roles, and modes. No output schema exists, so return value details are not expected, but the description could mention output format (e.g., list of discrepancies). Still, it is largely complete for safe invocation.

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?

Despite 0% schema description coverage, the description adds meaning for all parameters: apply's role (dry run vs action), item_ids (optional narrowing), and confirm (required when apply=true). It explains the relationship between parameters effectively.

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 tool's purpose: reconcile in-stock firearm serial numbers against FastBound, specifically finding guns FastBound shows as disposed but still active in inventory. This is a specific verb-resource combination and distinguishes from sibling tools like woo_reconcile.

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 explains the two modes (dry run with apply=false and actual removal with apply=true requiring confirm=true) and mentions optional item_ids for narrowing. However, it does not explicitly state when to use this tool vs alternatives or provide exclusion criteria, leaving some room for interpretation.

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