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

Goes well beyond the readOnlyHint/openWorldHint annotations: concrete rate limits (3 per IP per UTC day, 50 shared caller/ASN pool, 100 globally), the auth mechanism (Authorization: Bearer tt_…), the billing model (TidyTools credits), and the x402/Apify payment path with no account required. An agent knows the cost and failure profile before calling.

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?

Front-loaded with the core action and return behavior, then quotas last. The x402/Apify sentence is jargon-dense and only relevant to a subset of callers, keeping it just short of a 5, but nothing is redundant.

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?

With no output schema and only two annotations, the description carries the burden well: it covers return shape, auth, pricing, and quota. It omits the output format of 'readable content' (markdown vs. text) and error behavior, which are the remaining gaps for a fetch tool.

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?

With one fully described parameter at 100% schema coverage, the schema already does the work (baseline 3). The description adds meaning by repeatedly stressing the single-URL constraint ('one public URL', 'Use for one url'), reducing the chance of a misuse like passing a list.

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: 'Fetches one public URL as readable content', plus what comes back (limited free result + paid upgrade links). It does not name a distinguishing sibling such as read_url or extract_article, so the agent must infer differentiation from scope language alone.

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?

'Use for one url. Not for batch work or unrestricted monitoring' gives explicit when-to-use and when-not-to-use boundaries. It stops short of naming alternatives (read_url, extract_article, link_preview) that would settle ambiguous cases.

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