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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the burden is lower. The description adds genuinely useful behavioral context beyond that: the score's composite composition and the interpretive caveat that a strong Galaxy Score is not a statement about valuation. It does not disclose the return format or limit behavior, but those gaps are modest given the safety profile is fully annotated.

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?

Four sentences, with the core purpose front-loaded and zero filler: metric definition, interpretation caveat, and sibling routing each earn their place. Minor redundancy ('composite' followed by 'folded together') and awkward line-break formatting keep it just short of a 5.

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?

For a read-only tool with one optional parameter and no output schema, the description covers the essential context: what is ranked, by what metric, how that metric is composed, what the score means, and where to go for the breakdown. It stops short of stating the exact output shape (e.g., a ranked list of asset identifiers with their scores), which is the one meaningful addition for an agent invoking it.

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%, and the description never mentions the sole parameter `limit` or its behavior (maximum value, default, pagination). Per the rubric, the description carries the compensation burden at this coverage level and does not fulfill it — though the parameter's meaning is trivially inferable from its name, integer type, and default of 10, which keeps this above a 1.

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 opens with the exact deliverable — 'the assets with the strongest Galaxy Score right now' — and defines the metric precisely (0-100, composite of social volume, engagement, sentiment, and market health). It explicitly differentiates itself from get_asset_scores by naming it as the tool for the score breakdown, and clarifies what a high score does not mean (cheapness). An agent can identify this tool's output among 60+ siblings without guessing.

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?

The description explicitly routes to get_asset_scores for the breakdown and warns that a high score signals attention/health, not valuation, which implicitly excludes valuation-driven use cases. What it does not do is contrast itself with sibling ranking tools such as get_top_altranks or get_trending_assets, leaving when-to-use vs. those to inference.

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