Web page scrape

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

Annotations already declare openWorldHint=true and destructiveHint=false, so the description's main contribution is the cost model ('Flat fee per call'), which is decision-relevant and consistent with readOnlyHint=false and idempotentHint=false — repeat calls are billed. It does not mention auth requirements, rate limits, or failure behavior for unreachable pages, 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 short front-loaded fragments with no padding, and the core (fetch one page as text/markdown) leads. The trailing 'Always on /v1' is cryptic — it is unclear whether it means endpoint version, path prefix, or an API constraint — so it costs a little clarity for little gain.

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 the description should say more about what comes back, but the stated text/markdown return covers the essentials and the flat-fee notice covers cost. The nested `extra` object and the absence of any search-vs-scrape routing guidance leave meaningful gaps for a paid, open-world call.

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% across two parameters, so the description carries the full burden and it explains neither parameter. The `url` field is at least self-evident from its uri format, but `extra` — a nested free-form object with additionalProperties — is completely unexplained anywhere, leaving an agent no basis for populating it.

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 one web page') and specifies the return format ('as text/markdown'). The word 'one' signals single-page retrieval, which implicitly contrasts with the sibling carpe_web_search, but the description never names that sibling, so the differentiation must be inferred.

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?

Usage is only implied: an agent can infer this is for retrieving the contents of a known URL rather than discovering pages. There is no explicit when-to-use, no when-not, and no named alternative such as carpe_web_search for query-based discovery.

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