Extract Table

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It does not mention return format, how pageLimit affects extraction, the outputFormat options, the need for a valid sessionId, or behavior when no table exists. The one-sentence description provides minimal behavioral insight.

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?

The description is a single sentence that is concise and front-loaded with the action. It avoids fluff and is easy to parse. However, its terseness sacrifices useful context; still, as a concise statement it earns a reasonable score.

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 four parameters, an output format enum, and no annotations or output schema, the description is severely incomplete. It provides no information about return values, parameter usage, or prerequisites, making it insufficient for an agent to invoke the tool correctly in most scenarios.

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 schema lists four parameters with zero description coverage, and the tool description adds no parameter semantics. selector, pageLimit, sessionId, and outputFormat are entirely unexplained, leaving the agent to guess at their meaning. The description should compensate for the schema gap but does not.

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 extracts table data from the page, using a specific verb and resource. It distinguishes itself from sibling tools like extract_text and extract_form by focusing on tables, though it could specify the type of table (e.g., HTML table) for complete clarity.

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?

Usage is implied: an agent would use this when needing table data from a page. However, there is no explicit guidance on when to prefer this over extract_text or extract_form, nor any mention of prerequisites like an active session. The context is thin but not misleading.

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