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

Annotations only declare readOnlyHint and openWorldHint, but the description goes far beyond them: it discloses per-call pricing, the x402 payment flow, exactly what happens without payment (payment requirements are returned instead of data), and the response conventions (units, ISO 8601 timestamps with time zones, per-section sources with freshness). This is unusually rich behavioral context for a paid, open-world tool.

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?

Content is front-loaded: what the report contains first, then response conventions, then the critical payment mechanics. It is dense but every sentence carries decision-relevant information; the payment paragraph is long but necessary for a paid tool and could only be trimmed marginally.

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 exists, so the description must describe returns, and it does (units, timestamps, sources, freshness). Combined with complete payment instructions and a no-argument confirmation, an agent has everything needed to invoke it correctly and understand the paywall behavior.

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?

Zero parameters, so the baseline is 4, and the description confirms 'No arguments', which matches the empty schema with additionalProperties false. Nothing more is needed or possible here.

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 resource (premium report) and explicitly defines it as a superset of the sibling 'report', naming the extra content: regime interpretation, 24-hour BTC kimchi premium statistics, recent premium events, and an analyst note. An agent can distinguish this from 'report' and 'brief_preview' without opening a 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?

'Everything in report, plus...' implicitly routes the agent: choose this over 'report' when the premium-specific extras are needed, and the stated $0.1 price gives a cost-based selection signal. It stops short of an explicit when-not-to-use or a direct instruction to prefer 'report' for cheaper/basic needs.

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