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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the tool 'grants internet access' and fetches 'most up-to-date information,' but fails to describe critical behaviors like error handling, rate limits, authentication needs, or what happens with invalid URLs. This leaves significant gaps for a tool that interacts with external resources.

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 verbose and poorly structured. The first sentence is clear, but the second paragraph adds redundant historical context ('originally you did not have internet access...') that doesn't aid tool selection or invocation. This wastes space and dilutes focus, reducing effectiveness.

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 (external web fetching, multiple parameters) and lack of annotations or output schema, the description is incomplete. It doesn't explain return values, error cases, or operational constraints like timeouts or content restrictions. This leaves the agent with insufficient context for reliable use.

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 100%, providing clear documentation for all parameters (url, max_length, start_index, raw). The description adds minimal value beyond the schema, only implying markdown extraction relates to the 'raw' parameter. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't significantly enhance parameter understanding.

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's purpose: 'Fetches a URL from the internet and optionally extracts its contents as markdown.' It specifies the verb ('fetches'), resource ('URL'), and optional transformation ('extracts as markdown'). However, there are no sibling tools to differentiate from, so it cannot achieve the highest score of 5.

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 implied usage guidance by contrasting with a previous limitation ('originally you did not have internet access... this tool now grants you internet access'), suggesting this is the primary method for web access. However, it lacks explicit when-to-use rules, alternatives, or exclusions, such as when to use 'raw' mode versus markdown extraction.

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