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

No annotations provided, so the description carries the full burden. It discloses key behavior: deterministic, static HTML, no JS rendering. However, it omits details like error handling, response size limits, or what 'metadata' includes. The description adds value beyond the schema but is not exhaustive.

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 a single, well-structured sentence that front-loads the main action and key constraints. Every word serves a purpose: 'Fetches a URL' (action), 'returns clean article text/markdown plus metadata' (output), and the behavioral note. No redundancy or fluff.

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 fetch tool with no output schema and no annotations, the description covers the essential purpose and a key limitation (static HTML only). However, it lacks details on output format, metadata contents, expected error behavior, and prerequisites. It is adequate but not fully comprehensive.

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 0%, yet the description does not explain either parameter. It mentions 'Fetches a URL' but that is already obvious from the schema. The format parameter's enum is clear from the schema, but no additional context (e.g., that 'both' returns both text and markdown) is provided. The description adds minimal value beyond the schema for 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?

Description clearly states it fetches a URL and returns clean text/markdown and metadata. The verb 'Fetches' and resource 'URL' are specific. It distinguishes itself by noting 'static HTML only, no JS rendering', establishing its scope.

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?

No explicit when-to-use or alternatives, but the description provides clear context: it is for static HTML pages that yield clean article text. The absence of sibling tools reduces the need for comparative guidance. The 'static HTML only' note implicitly advises against using it for dynamic pages.

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