camofox_extract_structured_data

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

No annotations provided; description carries full burden. Describes the extraction mechanism and prerequisite but omits details like error handling (e.g., missing refs), whether extraction is synchronous, or if it modifies page state.

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 effective sentences with no fluff. Front-loaded with purpose and followed by a critical prerequisite. Every word earns its place.

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?

For a tool with 3 required params, nested schema, and no output schema, the description explains input format and prerequisite well. Missing details about output shape (though inferable from schema) and potential errors.

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 33%; only the 'schema' parameter has a description. The description adds meaningful details about the schema structure and x-ref usage, but 'tabId' and 'userId' lack explanation. Partially compensates for low coverage.

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 it extracts structured data using a JSON Schema with x-ref hints. It distinguishes from sibling tools (e.g., snapshot, click) by focusing on data extraction from the current page and explicitly requiring a prior snapshot call.

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 instructs to call camofox_snapshot first to populate the ref table. Provides clear context for when to use but does not mention when not to use or alternatives.

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