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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description does add one genuinely behavioral note — that direct upstream calls return only the purchase path and not the full paid payload, implying a cost/premium tier — but it is phrased ambiguously and never says what the tool's output contains or how scoring is bounded.

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?

Three sentences, but the first two are monetization boilerplate placed ahead of the only operational sentence, so the definition is not front-loaded. The space spent on 'Premium intelligence' and the x402 purchase path buys the agent nothing it can act on.

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, four undocumented parameters, and no explanation of what a scored 'opportunity' looks like, the description leaves the agent unable to predict results or fill optional inputs. For a read-only, open-world scoring tool this is well short of what 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 description coverage is 0% across four parameters, so the description must compensate and it largely does not. 'Supplied venue evidence' faintly maps to venue_observations, but symbol, stale_after_seconds, and minimum_liquidity_usd are never mentioned, leaving their semantics entirely to the JSON types.

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 only sentence describing actual work is 'Score a Robinhood Stock Token only from authoritative reference data and supplied venue evidence,' which gestures at scoring/ranking but never states what an 'opportunity' is or what the tool returns. The opening two sentences are about upstream MCP calls and an x402 purchase path, which describe the vendor's monetization rather than this tool's verb+resource, and nothing distinguishes it from siblings like rwa_analyze_asset or rwa_market_snapshot.

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?

There is a single implied constraint ('only from authoritative reference data and supplied venue evidence') but no statement of when to call this versus rwa_analyze_asset, rwa_compare_assets, or rwa_market_snapshot. An agent has no basis for routing between the seven siblings from this text.

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