fetch_url

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

The description only mentions that a BingWebmasterError is raised if the URL cannot be fetched. With no annotations, the agent lacks information on side effects, whether the operation is read-only, rate limits, or authorization requirements.

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 concise with a clear action and error note. It is front-loaded with the purpose, though the inclusion of 'self' in the args list without explanation slightly reduces clarity.

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?

The description does not mention the output of the fetch (despite an output schema existing), nor does it cover prerequisites, permissions, or the scope of the operation. The agent is left to assume the result.

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 input schema has 0% description coverage, and the description explains 'site_url' and 'url' but not the required 'self' parameter. The agent cannot understand the role of 'self', and URL format or restrictions are omitted.

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 tool requests Bing to fetch a specific URL immediately. While it does not explicitly differentiate from similar tools like 'submit_url' or 'get_fetched_url_details', the intent is clear for a fetch operation.

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 this tool versus alternatives, such as submitting a URL for crawling or retrieving previously fetched results. The description lacks context for appropriate usage.

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