ie_grid

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

Discloses that it auto-picks the table, returns headers and rows as header-keyed dicts, and is app-agnostic. No annotations present, so description carries full burden; it adequately covers read-only extraction behavior.

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 concise sentences with no wasted words. Front-loaded with the core purpose, then details.

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?

Covers return format, auto-detection, and app-agnostic nature. Lacks details on error handling or what happens when no grid is found, but overall sufficient for a single-purpose extraction 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 100%, so the description adds minimal additional meaning beyond the schema. The mention of auto-selection and return format provides some context but does not significantly enhance parameter understanding.

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 explicitly states 'Extract a tabular grid as structured rows' with a specific verb and resource. It distinguishes from siblings by focusing on grid extraction vs general text or HTML retrieval.

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?

Provides guidance on auto-picking the table or passing a table_id. Does not explicitly exclude other scenarios, but context is clear.

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