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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, open-world), and the description adds the crucial non-obvious behavior: this call is paid at $0.015 and returns x402 payment requirements plus a URL rather than the content directly. That payment-flow disclosure is exactly the kind of context annotations cannot convey.

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 price and identity are front-loaded, and the content enumeration is dense but each item carries information. The single long sentence is slightly heavy, though the closing free-sample pointer is well placed.

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 still tells the agent the response format (JSON + markdown), the field coverage, the 7-day lookahead, and the payment-challenge behavior. An agent can decide and call correctly without further information.

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 takes zero parameters, so there is nothing to disambiguate; the baseline for a no-param tool applies. Nothing in the description is needed here beyond noting the absence of filters, which the schema already establishes.

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 ('the full latest twice-daily crypto research brief') and enumerates its contents (headline, sentiment, funding, watchlist, news, macro). It is clearly distinguishable from the free-sample sibling get_sample_brief and from narrower siblings like get_sentiment or get_outlook.

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?

Gives an explicit use case ('for agents that need a ready market summary for a user or a daily report') and names the free alternative get_sample_brief with a URL. It does not, however, contrast with other paid research siblings such as get_outlook or get_narratives_weekly, so the routing guidance is only partial.

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