Jina Web Reader

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

No annotations are provided, so the description must disclose behavioral traits. It fails to mention rate limits, extraction format, error handling, or limitations (e.g., does it handle JavaScript? Blocked sites?). This is insufficient for a web reader tool.

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 single sentence is concise but lacks necessary detail. It is not overly verbose, but it sacrifices completeness for brevity. A balanced approach would add a second sentence with key behavior.

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 tool's complexity (web reading) and lack of output schema, the description is incomplete. It does not explain what is returned (e.g., text, metadata), pagination handling, or timeouts beyond the schema.

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 schema itself documents each parameter. The description adds no extra meaning beyond 'read and extract content.' With high schema coverage, baseline is 3.

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 action (read and extract) and the resource (web page). However, it lacks specificity about what exactly is extracted and doesn't differentiate from potential siblings (none exist). A score of 4 reflects a clear purpose but no sibling differentiation.

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 given on when to use this tool, when not to, or any prerequisites. The description is generic and does not help the agent decide based on context.

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