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

With no annotations, the description carries the full burden, and it does disclose useful traits: text is returned verbatim, nothing is per-patron, nothing is computed, and two callers get identical bytes (deterministic/idempotent read). However it omits cost, rate limits, and auth behavior, and 'nothing is per-patron' sits oddly against the schema's npub 'for credit billing' requirement.

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 purpose is front-loaded in the first sentence, which is good. But the remaining prose about server-side rendering, empty mount divs, and scraping is largely self-justification that does not help an agent select or invoke the tool.

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 no explanation, and the description adequately conveys that this is a static orientation document. The only real gap is the unmentioned billing/npub requirement, which matters for a tool whose schema demands a credential.

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 50% (dpop_token undocumented) and the description adds nothing about either parameter. It never mentions npub, even though the schema marks it required for credit billing, and the 'nothing is per-patron' claim arguably conflicts with that requirement.

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+resource: it returns prose explaining 'what this service is and how to play it,' and identifies it as the same text as /llms.txt. An agent can tell it apart from siblings like oracle_about or service_status, though it never explicitly contrasts itself with them.

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 implied rather than stated: it is framed as the 'front-door answer' an MCP-arriving agent should read instead of scraping the website. There is no explicit 'use this when X, not Y' guidance and no mention of when the orientation is unnecessary.

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