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

Annotations only declare read-only and open-world; the description adds genuinely useful behavior the schema cannot express: robots.txt and noai opt-out compliance, PDF failover, and a concrete quota (25/day free, 500 with credit). It does not disclose failure modes or what happens when opt-outs block a fetch, keeping it below 5.

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?

Three dense sentences that front-load the core action, with quota and compliance details trailing. The leading 'Dirtsmith-built.' is arguably dead weight and the parenthetical '(actually executes)' is awkward, but overall there is little waste.

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?

An output schema exists, so return values need not be re-explained, and quotas/compliance are covered. The real gap is parameter meaning: max_chars is undocumented in both schema and description, leaving the agent guessing on an optional-but-useful control.

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%, so the description must carry the burden for three parameters. It indirectly explains the 'credit' parameter via the 500-call unlock, but 'max_chars' is never mentioned and the url parameter gains nothing beyond the obvious name. Partial compensation for a low-coverage 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?

States a specific verb and resource: 'Fetch a URL and return clean markdown text', which is unambiguous and distinct from siblings like pdf_tables or json_validate. The '(actually executes)' aside is odd but does convey the tool performs a real network fetch rather than planning one. No sibling is named, so it stops short of 5.

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?

'free failover for PDFs' hints at when to prefer this over the pdf_tables sibling and the quota line implies a cost decision, but there is no explicit when-to-use or when-not-to-use guidance. The agent must infer the routing from the PDF clause.

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