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

Annotations already declare readOnly/openWorld/non-destructive, so the safety profile is covered. The description adds genuinely useful behavioral context the annotations cannot: it is an aggregating synthesis (X + RobinX caller-lift + on-chain), it is 'skeptical by design', and it costs $0.04 or is covered by a plan key — cost/payment behavior is material for an agent deciding whether to call it.

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?

One dense but front-loaded sentence that leads with the core capability, plus a short parenthetical for cost/entitlement. Every clause carries information (outputs, data sources, stance, price) and nothing is padded.

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?

No output schema exists, so the description carries the return-value burden — and it does enumerate what comes back (narrative, sentiment, conviction, red flags, early-caller activity). Combined with the payment note and read-only annotations, an agent has enough to call it correctly, though the lack of any routing guidance among the many sibling tools leaves a small gap.

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?

Single required parameter with 100% schema coverage ('Token contract address 0x…'), so the schema already documents the input. The description adds only the scope qualifier 'Robinhood Chain token', which is marginal beyond the structured field. Baseline 3 applies when the schema does the heavy lifting.

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+resource (real-time X synthesis for a Robinhood Chain token) and enumerates the outputs: narrative, sentiment, conviction, red flags, proven early-caller activity. The 'not follower counts' contrast hints at differentiation, but it never names the siblings it competes with (e.g. robinx_social_momentum, robinx_verdict), so an agent must still infer its place in the family.

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?

Usage is only implied: reach for it when you want a fused social read on a Robinhood Chain token. There is no explicit when-to-use vs when-not, nor any pointer to the alternative tools (robinx_signals, robinx_verdict, robinx_social_momentum) that also cover token sentiment.

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