Caller Report Card (free)

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

Annotations already establish that this is a read-only, open-world, non-destructive operation, but the description adds substantial behavioral context: it is measured against real on-chain price since chain genesis, and calls are preserved as captured so deletion does not scrub the record. It also defines what early_rate and momentum_rate mean, which is useful signal beyond the annotations.

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-loads the core value: a free measured track record with specific report-card metrics. The provenance/immutability sentence and the usage recommendation each add distinct value, with no filler.

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 must explain what comes back, and it enumerates the report-card fields: early_rate, momentum_rate, median 1h forward return, coordinated-cluster flag, and recent calls. It also explains the measurement basis and persistence of records, which is sufficient context for an agent to invoke it correctly.

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?

There is only one parameter, handle, and schema description coverage is 100%; the schema already documents that the handle may be provided with or without '@'. The description says 'any X account' but adds no further format, validation, or example detail beyond the schema, so the baseline of 3 applies.

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 resource and outcome: a measured track record for an X account that has called Robinhood Chain tokens, including named metrics like early_rate, momentum_rate, and median 1h forward return. It is clear what the tool produces, but it does not explicitly differentiate itself from sibling tools such as robinx_callers or robinx_caller_calls.

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 closing sentence, 'Use before trusting any "alpha caller",' gives a clear decision context for invoking the tool. It does not state when not to use it or name alternative tools for related needs, so it falls short of full when/when-not/alternatives guidance.

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