extract

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

With no annotations and a terse description, the tool's behavioral traits are opaque. It does not disclose whether extraction is read-only, modifies state, requires authentication, or has side effects. The description only states its action, missing critical context for safe invocation.

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?

While the description is extremely short, it fails to provide necessary details. Conciseness should not sacrifice completeness; here, the sentence is too terse to be useful, especially given the absence of parameter descriptions and annotations.

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 low schema coverage, no output schema, no annotations, and a vague description, the tool definition is incomplete. An agent cannot reliably determine how to invoke this tool or what to expect as output, making it nearly unusable without prior context.

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 parameter 'instruction' lacks any description in the schema (0% coverage) and is not explained in the tool description. The agent has no idea what format or content the instruction expects (e.g., CSS selector, natural language). This is a severe gap.

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 'Extract data from the page,' which clearly indicates a read operation to retrieve data. However, it does not specify what kind of data (e.g., text, attributes, structure), making it vague compared to sibling tools like 'observe' which may also involve data extraction. The purpose is understood but lacks precision.

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 is provided on when to use 'extract' versus alternatives like 'observe' or 'act'. The description does not indicate prerequisites (e.g., page must be loaded), nor does it mention when extraction is appropriate. This leaves the agent to infer from context.

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