ingest_url

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

There are no annotations, so the description carries the burden. It discloses that client-rendered (React/Vue) pages may return little content, which is useful. However, it does not mention other behavioral aspects such as handling of invalid URLs, redirects, rate limits, or what the 'structural blueprint' contains.

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 two sentences with no filler. It front-loads the main operation and adds a valuable caveat in the second sentence.

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?

With one required parameter and no output schema, the description provides a basic understanding but leaves the return format vague ('structural blueprint'). The pointer to ingest_html helps, but a self-contained description would be more complete.

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 documents the single 'url' parameter with the description 'Public page URL to analyse', providing 100% coverage. The tool description adds no further semantic detail, so the baseline 3 applies for high schema coverage.

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 fetches a public URL and parses it into a structural blueprint. It uses a specific verb ('Fetch') and resource ('public URL'), and references ingest_html for the parsing details, which helps distinguish it from sibling tools like ingest_html and general fetch functions.

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 implies a use case (fetching URLs for parsing) but does not explicitly state when to choose this over ingest_html. The note about client-rendered pages provides a caution but not a clear alternative selection rule. The reference to ingest_html suggests it is the canonical tool, but the guidance is implicit.

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