read_url

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

Annotations already declare readOnlyHint=true, and the description adds that it is 'free status' and that it returns no secrets. This is a useful behavioral guarantee beyond the annotation, clarifying what the tool does not expose. It does not contradict annotations.

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 a single concise sentence that front-loads the key information (status types) and ends with a security guarantee. Every word earns its place.

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?

No output schema is provided, but for a simple status tool the description covers the main return categories (environment, network, paid offer, availability) and the 'no secrets' caveat. It is complete enough for an agent to invoke correctly, though the exact return format is unspecified.

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 tool has zero parameters and the schema coverage is 100% (vacuous). Per the rubric, a 0-param tool gets a baseline of 4. The description adds no parameter details, but none are needed.

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 the tool reports status for environment, network, paid offer, and availability of the paid tool. It is specific about what it checks and clearly distinct from the sibling read_url. It lacks an explicit verb like 'check' but the purpose is evident.

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 does not provide explicit guidance on when to use this tool versus alternatives. It is implied that one calls this to get service status, but no when-not or exclusion conditions are stated. For a simple status tool this is acceptable but still lacks explicit routing.

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

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

The description goes well beyond the readOnlyHint/openWorldHint annotations by disclosing robots.txt compliance, refusal conditions (private/internal/non-public, oversized, non-HTML), one-page-only behavior, no link following, the paid/PaymentRequired flow, and the untrusted nature of returned content. This is exemplary behavioral disclosure.

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 long but every sentence earns its place: usage guidance is front-loaded, behavioral constraints are compactly enumerated, and the payment/trust warnings are essential for correct invocation. Nothing feels 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 one parameter and no output schema, the description carries the full burden and succeeds: it explains what is returned (markdown with title, byline, language, word count, SHA-256), what is refused, how payment works, and how to treat the content. An agent has everything needed to invoke it correctly.

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 coverage is 100%, so the schema already documents the single url parameter. The description reinforces that the URL must be public and http(s), but it does not add substantially new semantic detail beyond the schema's own description.

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 and resource: fetches one public web page and returns it as clean markdown. It explicitly distinguishes itself from searching, crawling, and login-gated content, so an agent can differentiate it from other tools without opening the schema.

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 a crisp when-to-use condition ('when you already have the URL of a specific public page and need its readable text') and explicitly lists exclusions: not for searching, not for crawling, not for login-gated pages. This is the clearest possible usage guidance.

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