extract_with_gate

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

Discloses the key behavioral trait of the gate (review queue for uncertain values) without annotations. Does not cover authentication or rate limits, but the core behavior is well explained.

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?

Three focused sentences: purpose, behavior, and field list. No redundant information.

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?

Adequate for a 2-parameter tool with no output schema. Explains extraction and gating. Could note what happens if all values are high-confidence or all uncertain, but overall sufficient.

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 basic descriptions. The description adds value by enumerating valid field names (invoice_number, total_amount, date, email, vendor_name), which is not in 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?

Clearly states it extracts fields from a document and lists the specific fields: invoice_number, total_amount, date, email, vendor_name. Distinguishes from siblings by explaining the gating behavior.

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?

Explains that high-confidence values return immediately and uncertain values go to a review queue, guiding when to expect immediate vs. deferred results. Does not explicitly state when not to use or mention alternatives, but siblings hint at post-extraction steps.

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