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

With no annotations, the description carries the behavioral burden. It discloses that the tool performs a fetch, converts to Markdown, and relies on the site's markdown content negotiation, plus expected input format. It doesn't mention edge cases like 404s or empty content, but core behavior is clear.

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?

Two short sentences: first states action and result, second gives input format and examples. No filler or redundancy.

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 one-parameter, read-only page fetcher with no output schema, this is complete: it names the domain, the path format, examples, and the Markdown return format. Nothing critical is missing for invoking it correctly.

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 coverage is 100%, so the baseline is 3; the description adds value with explicit path examples ('/' and '/blog/core-web-vitals/') and reinforces that path is site-relative and must start with '/'. This goes beyond the schema field description.

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?

Begins with 'Fetches any page on built2winweb.com' – a specific verb, resource, and scope. It also states the result is converted to Markdown, which distinguishes it from sibling tools like get_contact or search_site that serve different content or purposes.

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?

Gives clear context: use this tool to retrieve any site page by passing a site-relative path, with concrete examples. It does not explicitly name alternatives or state when not to use it, though the 'any page' framing implies it is the general-purpose page-fetch tool.

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