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

With no annotations, the description carries the full burden and does so: data rewritten every 30 s, 503 refusal if older than 180 s, 404 for unseen mints, no charge on failed calls, and $0.02 USDC x402 pricing. It also disclaims research-only status. These are exactly the operational facts an agent needs.

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?

Long but front-loaded: the return contents lead, then freshness/error semantics, then pricing. Almost every clause adds operational value, though the single dense paragraph runs on and the return enumeration could be tightened given an output schema 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?

An output schema exists so return values need not be explained, yet the description still orients the agent on what is and isn't included. Combined with freshness, error, and billing semantics, nothing needed to invoke this confidently is missing.

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 one required parameter (mint) and schema description coverage is 100%, so the schema already documents it fully. The description adds no format, constraint, or example beyond what the schema provides, 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?

States a specific resource (a Solana mint's recorded desk data over the last 48 h) and enumerates exactly what is returned: safety gate, scout scores, scanner-card grade, trader action, shadow outcomes, last closed paper trade. An agent can distinguish this from siblings like rh_token_verdict or sol_callers_leaderboard 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?

Clearly frames the trigger condition (want everything the desk recorded on a given mint) and the negatives (no thesis, no bot card, no chat content), which tells the agent when this is the wrong tool for narrative/chat data. It does not explicitly name an alternative sibling for cases the exclusions cover, so it stops short of full routing guidance.

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