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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the extraction action without explaining return format, handling of multiple tables, error conditions, or limitations (e.g., dynamic content). This leaves significant behavioral ambiguity.

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?

One concise sentence with no superfluous words. It gets straight to the point and is easy to parse.

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 the absence of annotations, output schema, and the minimal description, the tool is under-specified. It doesn't mention what the output looks like, whether it returns raw HTML, parsed tables, or handles missing tables. For a tool with a single param, it's minimally viable but leaves important gaps.

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 single 'url' parameter is self-explanatory from the description and tool name, and the schema defines it as required with string type. The description does not add detail beyond that, but the param's meaning is clear from context. Schema coverage is 0% yet the param is so obvious that a 3 is appropriate.

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 states a specific action ('Extract HTML tables') and a specific source ('URL'), clearly differentiating it from broader extraction tools like extract_url or ocr_table_url. However, it lacks explicit contrast with sibling tools, so not a full 5.

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?

The description provides no guidance on when to use this tool over alternatives like extract_url or ocr_table_url, nor does it mention any preconditions or alternatives. It simply states the function.

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