ai.extract

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

With no annotations, the description carries the full burden. It discloses that the tool will fetch a URL and extract data, but omits important behavioral details: whether it is read-only, error handling, authentication, rate limits, or output format. The description is too minimal for a tool that performs an external fetch.

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 sentences, no fluff. The first sentence explains the action, the second provides usage context. Front-loaded and efficient.

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 that there is no output schema and three parameters, the description is complete enough for basic understanding but lacks details on return format, URL requirements, and potential side effects. For a tool that fetches arbitrary URLs, more context would be beneficial.

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 description coverage is 67% (two of three params have descriptions). The description adds no per-parameter details beyond what the schema already provides. It reiterates the schema parameter's purpose but does not compensate for the missing description on the 'url' parameter.

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?

Description clearly states the tool fetches a URL and extracts typed data according to a user-supplied JSON Schema. This distinguishes it from sibling tools like ai.summarize or ai.describe-image, which handle different tasks.

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?

Explicitly says 'Use when you need a structured payload conforming to your own shape', providing clear context. However, it does not mention when not to use it or name alternatives like ai.summarize for unstructured text.

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