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

With no annotations provided, the description carries the full burden of behavioral disclosure. It meaningfully reveals that the signals are AI-operated and disclosed, refresh every 10 minutes, and incur a payment cost. These traits go beyond the core function and inform the agent of nontrivial operational behavior, though payment mechanics and failure modes are not detailed.

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 description is compact and front-loaded with the core offering, followed by essential operational facts (update frequency, payment). Every sentence contributes distinct information: what the tool returns, its AI/disclosed nature, freshness, and cost. No filler or repetition exists.

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?

For a zero-parameter tool with no output schema, the description is quite complete: it names the exchange, pair count, score range, included data fields, update cadence, and payment requirement. The only notable gap is that it does not describe the payment flow or response format, but the essential invocation context is present.

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 input schema has zero parameters, so the baseline is 4. The description adds value by enumerating what the tool returns—scores, price, ATR%, and reasons—which helps the agent interpret outputs even though there is no output schema. It does not need to explain parameters since none exist.

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 clearly identifies the function: providing ranked crypto signal scores for 20 USDC pairs on Coinbase. It enumerates specific output fields (score range, price, ATR%, reasons), which makes the tool's purpose concrete and distinguishable from the broader sibling set. However, there is no explicit action verb such as 'get' or 'retrieve,' so it falls just short of the highest bar.

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?

The description includes operational prerequisites like 'Updated every 10 min' and 'Requires payment of $0.001 USDC,' but gives no guidance on when to choose this tool over siblings like preview, price, or report. There is no mention of alternatives or exclusions, leaving usage decisions to inference.

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