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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions content extraction and image URL inclusion, but doesn't cover important aspects like error handling (e.g., invalid URLs, network failures), rate limits, authentication needs, privacy implications, or what happens when maxLength is exceeded. The description is insufficient for a tool that interacts with external resources.

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 perfectly concise with two clear sentences that each add value. The first sentence establishes the primary function, and the second adds important behavioral detail about image handling. No wasted words or redundant information.

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 tool with 4 parameters, no annotations, and no output schema, the description provides adequate basic functionality explanation but lacks sufficient detail about behavioral characteristics, error conditions, and output format. The absence of sibling tools reduces complexity, but the description should do more to compensate for the lack of structured metadata.

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 description doesn't mention any parameters directly, but with 0% schema description coverage, it doesn't compensate for the lack of parameter documentation. However, the tool has 4 parameters with clear schema definitions (url, maxLength, startIndex, raw), and the description's focus on the core functionality provides some context. The baseline would be lower if the schema were less informative.

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's purpose with specific verbs ('retrieves', 'extracts') and resources ('URLs from the Internet', 'content as markdown'), and explicitly mentions handling of images. It distinguishes what the tool does without relying on the generic name 'fetch'.

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 usage for retrieving and converting web content to markdown, but provides no explicit guidance on when to use this tool versus alternatives (though no sibling tools are listed). It lacks information about prerequisites, error conditions, or performance considerations.

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