extract_html_table

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

No annotations provided, so description carries full burden. It discloses output is a JSON array but omits important behaviors: handling of malformed HTML, multiple tables, table structure, or error cases. Minimal for a data extraction tool.

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?

Extremely concise with two sentences and a parameter list. Front-loaded with purpose, but lacks additional details that could be included without bloat.

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?

With a single parameter and no annotations, but with output schema, the description adequately states 'structured JSON array' but doesn't detail the schema structure (e.g., rows/columns, handling of multiple tables). Moderately complete for a simple tool.

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 compensate. It adds a brief hint 'HTML content containing tables' but doesn't specify format, required structure, or behavior for no tables. Baseline adjusted due to schema gap but parameter is simple.

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 HTML tables into a structured JSON array, using specific verb and resource. It distinguishes itself from all sibling tools, none of which perform HTML table extraction.

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?

No guidance on when to use this tool vs alternatives, no mention of prerequisites or edge cases (e.g., multiple tables, malformed HTML). The description only lists the parameter without usage context.

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