woo_reconcile

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

No annotations provided, so description carries full burden. It mentions 'confirm=true' but doesn't explain what confirm does, nor does it disclose if the operation is destructive, reversible, or requires permissions. Lacks behavioral context beyond the basic push action.

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?

Description is two sentences and a phrase, efficiently conveying purpose. Could be clearer but is appropriately sized.

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 no output schema, no annotations, and 0% schema coverage, the description is incomplete. It lacks details on return values, error scenarios, and parameter behavior, which are critical for a tool that pushes data.

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%, so description must add meaning. It only mentions 'confirm=true' but doesn't explain the parameter or item_code. Minimal value added over the schema.

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 the tool pushes item-level product and all Active Serial Nos for an item in one call, specifically for initial listing of per-serial firearms. This distinguishes it from sibling tools like push_serial_to_fastbound or woo_push_item.

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?

Provides explicit context: suitable for initial listing of per-serial firearms where everything goes live at once. However, no mention of when not to use it or alternatives, though the specificity implies a niche use case.

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