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

No annotations are provided, so the description carries the burden. It discloses limited behavior: a free trial allowance ('5 free trial calls per signed wallet'), but does not mention auth requirements, rate limits, data scope, or lifecycle. Missing important behavioral context for a data 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?

Brief and front-loaded with the core concept, followed by a useful trial note. Every sentence earns its place, though the trial information might belong in annotations rather than description.

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 and vague parameter semantics, the description is incomplete. An agent cannot determine what response format to expect, how to format pair/symbol values, or what 'per signed wallet' means in practice. More behavioral and data context is needed.

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% for the two parameters (pair and symbol), but parameter descriptions are generic ('Pair to process' / 'Symbol to process'), leaving ambiguity about format, examples, or which is required. Since coverage is high, baseline 3 is appropriate; description adds no extra meaning beyond the schema.

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 provides 'Perpetual funding rates' which identifies the resource, but does not specify a verb or action. It distinguishes somewhat from other x402-* financial tools, but the name already implies this. The trial mention adds context but not purpose clarity.

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?

No guidance on when to use this tool versus alternatives like get_stats or other market data tools. The free trial note suggests a usage constraint but does not explain scenarios or exclusions.

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