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

The readOnlyHint annotation already indicates a safe read operation, so the description's burden is lower, but it adds no behavioral context beyond that. It mentions 'live Chainlink price' but does not disclose what the tool actually does when invoked (e.g., returns a list, fetches current data, or any constraints). No side effects or limits are described.

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 a single, compact sentence with no filler. It is appropriately short and has no unnecessary words, achieving high conciseness and straightforward structure.

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?

Without an output schema, the description must convey the return value, but it does not explicitly state what the tool returns. The phrase 'what a muse may buy' implies a list of tradable assets, but it is not explicit about the output format (e.g., array of tokens with prices). An agent cannot be certain whether it returns a single item or a list, making the description incomplete for a zero-param tool.

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 tool has zero parameters, and the schema is empty (100% coverage). Per the baseline for 0-param tools, a score of 4 is appropriate. The description adds nothing about parameters because none exist, and no additional meaning is needed.

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 is a noun phrase ('Robinhood Stock Tokens with a live Chainlink price') rather than an action statement. It does not state what the tool does (e.g., 'returns a list of...'), leaving the agent to infer the operation. It does identify a resource (tradable stocks) but lacks a clear verb or explicit purpose.

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?

No guidance is provided on when to use this tool versus its siblings like metamuse_price or metamuse_quote. There is no mention of alternatives, conditions, or exclusions, so an agent has no help in selecting it.

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