fetch_content

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

With no annotations, the description must disclose behavior, but it only states it fetches and parses content. It does not mention whether it executes JavaScript, handles errors, follows redirects, or any authentication/rate-limit implications, leaving the agent without behavioral transparency.

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 brief and front-loaded with the purpose, but includes an 'Args' section listing 'ctx' which is not present in the input schema, adding unnecessary (and possibly confusing) content.

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 simple single-parameter tool, the description covers purpose and parameter semantics, but lacks usage guidance and behavioral details that would be expected given no annotations; overall it is minimally adequate.

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 only defines 'url' as a string with no description; the description compensates by defining 'url' as 'The webpage URL to fetch content from', adding meaning beyond the bare schema. The mention of 'ctx' is not in the schema and may be an implementation detail.

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 uses a specific verb ('Fetch and parse') and resource ('webpage URL'), clearly distinguishing this content-fetching tool from the sibling 'search' tool which searches rather than fetches a specific URL.

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?

It provides clear context that this tool fetches a specific webpage URL, but it does not explicitly state when to use it instead of the sibling 'search' tool, nor does it give any exclusions or alternatives.

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