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

Annotations already establish readOnly, idempotent, and non-destructive behavior. The description adds useful behavioral context: the output is Markdown or stripped text, limited to 40,000 characters, and restricted to the blvigil.com domain. No contradiction with annotations.

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?

A single, front-loaded sentence communicates the action, scope, format, and limit with no filler. Every element earns its place.

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 tool, the description covers domain, output format, and truncation limit, which is sufficient context given the annotations and sibling tools. It could clarify the absent format-selection parameter, but nothing essential is missing for basic invocation.

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 schema only defines url as a URI, and schema description coverage is 0%, so the description must compensate. It adds meaningful domain and single-page context, but it does not explicitly explain how the url parameter maps to the Markdown/text output choice or how an agent should obtain a valid page URL.

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 states a specific verb (read), a clear resource (one blvigil.com page), and the output form (Markdown or stripped text) with a length cap. This distinguishes it from sibling tools like search_pages, which search rather than read.

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 phrase 'Read one https://blvigil.com page' clearly signals the tool is for fetching a single page from a specific domain Pitch. It does not explicitly name alternatives or state when not to use it, but the context is clear enough for an agent to route correctly beside search_pages and site_info.

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