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

The description adds substantial behavior beyond the annotations: it explains the return shape (limited free result plus paid upgrade links), payment via x402 through Apify without an account, and detailed rate limits by IP, shared AI caller/ASN pool, and global daily cap. These details are highly relevant for invoking the tool correctly and understanding access constraints.

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 compact and front-loads the core purpose. Every sentence is relevant, though the ordering mixes return/payment information before usage boundaries, making the structure slightly less crisp than it could be.

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 one-parameter conversion tool, the description covers purpose, usage limits, return expectations, payment requirements, and rate limits. It does not fully specify the exact return structure, but no output schema exists and the implied Markdown result is clear enough.

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?

There is only one parameter, and the schema already describes it at 100% coverage as 'One text or HTML fragment.' The description reinforces the single-fragment constraint with 'one supplied HTML fragment' and 'Use for one text,' but adds little syntax or formatting guidance beyond the schema.

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 gives a specific verb and resource: converts one supplied HTML fragment to Markdown. It also scopes the tool to a single text, which helps distinguish it from batch or monitoring tools, but it does not name or directly contrast with sibling alternatives such as extract_article or read_url.

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 clearly states when to use the tool ('Use for one text') and when not to use it ('Not for batch work or unrestricted monitoring'). It lacks explicit routing to alternative sibling tools, so it falls short of full alternative guidance.

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