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

With no annotations provided, the description carries the full behavioral burden and discloses the license-key requirement, purchase URL, output shape, and free-tier limitation. It does not cover rate limits, maximum batch size, or per-URL failure behavior beyond the success flag, but the core behavior is well exposed.

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 appropriately short and front-loads the core action and batching scope. The purchase link is useful for auth but slightly promotional, keeping it from a perfect score.

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?

Given the output schema exists, the description need not explain return values but does so anyway, and it adds necessary license context with no annotations available. Missing details about maximum batch size and per-URL error handling prevent a perfect score.

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% for the single urls parameter, so the description must add meaning. It clarifies that urls is a collection of public URLs and that the result is a list, but it does not specify format constraints, batch size, or examples beyond the schema's array type.

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 (convert), resource (multiple public URLs), output format (clean Markdown), and batching scope ('in one call'). It distinguishes itself from the single-URL sibling by noting 'Free tier is single-URL only,' making the batch distinction unambiguous.

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?

It gives clear context: this tool requires a WEB2MD_LICENSE_KEY env var and is for multiple URLs, while the free tier is single-URL only. It does not explicitly name the sibling tool as the alternative, but the condition for choosing batch vs. single is effectively communicated.

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