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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive semantics. The description adds meaningful interpretive context: it explains the 0-100 Galaxy Score scale, AltRank's '1 is best' orientation, and warns that the composite alone can mislead—agents must inspect component breakdowns to know whether movement was sentiment- or volume-driven. This goes beyond the structured metadata.

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 well-structured and front-loaded: the first sentence states exactly what the tool returns, the second defines the metrics, and the third delivers a critical caveat. Every sentence earns its place, and the all-caps warning effectively emphasizes the need to read the component breakdown.

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?

The tool has no output schema and no parameter documentation, so the description carries the full burden. It explains what the metrics mean and that components exist, but it does not describe the component names, the response envelope, or how `symbol` is resolved. This leaves some context that an agent would need in order to fully interpret the result.

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 sole parameter `symbol` has no description in the schema (0% coverage), and the description does not explain the expected format, resolution rules, or allowed values. It only implies the tool is per-asset via 'An asset's'. With such low schema coverage, the description fails to compensate for the missing parameter semantics.

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 specifies the resource (an asset's Galaxy Score and AltRank) and the output's core purpose (with the components behind each). This clearly distinguishes it from ranking-focused siblings like get_top_galaxy_scores or get_top_altranks, which serve a different scope.

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 explicit guidance is given about when to choose this tool over alternatives such as get_asset_fundamentals or get_top_altranks. The warning to read components is interpretive, not a usage rule. An agent must infer from the name and sibling list that this is the single-asset score endpoint.

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