fetch_urls

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Retrieve web page content' implies a read operation, it doesn't mention potential side effects (e.g., network requests, rate limits), authentication needs, error handling, or what format/content is returned. The description is minimal and lacks crucial operational context.

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, efficient sentence that communicates the core purpose without any fluff. It's appropriately sized for a tool with well-documented parameters in the schema, though it could benefit from additional context about when to use it.

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?

For a tool with 10 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what 'web page content' means in practice (HTML? text? metadata?), how results are structured for multiple URLs, error conditions, or performance characteristics. The agent lacks crucial information to use this tool effectively.

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 description mentions 'multiple specified URLs' which aligns with the 'urls' parameter, but adds no additional semantic context beyond what the comprehensive schema already provides (100% coverage). With excellent schema documentation, the baseline is 3 even though the description offers minimal parameter insight.

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 ('Retrieve web page content') and target ('from multiple specified URLs'), making the purpose immediately understandable. It distinguishes from the sibling 'fetch_url' by specifying 'multiple' URLs, though it doesn't explain the functional difference between the two tools beyond that.

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?

The description provides no guidance on when to use this tool versus the sibling 'fetch_url' or 'browser_install'. It doesn't mention any prerequisites, limitations, or alternative scenarios. The agent must infer usage from the tool name and parameters alone.

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