extract

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

Describes the full extraction strategy fallback order, the return format ({strategy, confidence, data, tried}), and the behavior when a specific strategy is forced. No annotations provided, but the description covers all behavioral aspects.

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?

Two sentences: first explains the algorithm and return, second explains usage and parameter override. No wasted words, front-loaded with key 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?

Despite no output schema, the description fully explains the return structure and behavior. Covers algorithm, usage, and parameter control. Complete for a tool with one optional parameter.

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?

The only parameter 'strategy' is described in schema with a brief description. The tool description adds value by listing all possible values and explaining the effect of passing a specific strategy (force extractor).

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: 'Auto-strategy structured-data extraction' with a specific fallback order. It distinguishes from sibling tools like extract_cards, extract_list, extract_table by being a generic one-shot extractor.

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?

Explicitly tells when to use ('one-shot...when you don't want to plan the strategy yourself') and how to force a specific strategy. No alternative tools mentioned but provides clear usage context.

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