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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds a genuine behavioral trait beyond that: 'Aggregates only; nobody is named,' which tells the agent results are privacy-preserving and contain no per-entity attribution. It also notes unlocks come 'with proof.' It does not address freshness or result shape, but the annotations lower the bar.

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?

Front-loaded with the scope ('Robinhood Chain as a whole') before the view enumeration. The second sentence is dense but each clause carries distinct content; there is no filler. Slightly cryptic phrasings ('a map', 'beside market attention') keep it from 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?

With no output schema, the description compensates by describing what each view surfaces, and it covers the view modes plus the default. Remaining gaps are the concrete response shape and the effective default for `view` (only implied). For a read-only, zero-required-parameter aggregate tool, this is close to sufficient.

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 coverage is 67%, and the enum for `view` carries no per-value descriptions in the schema, so the description does the heavy lifting by explaining what each mode returns (per-day metrics, the weekly rollup, an archived ISO week, scheduled HoodLock unlocks, build momentum vs market attention). It also clarifies that 'days' is the default and how its meaning shifts per view. This adds meaning well past the schema text.

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 the resource unambiguously: chain-level ('Robinhood Chain as a whole') versus the project/token-level siblings like get_project_snapshot or lookup_token. It is an overview/aggregate tool, so the lack of a strong action verb is acceptable; an agent can tell it apart from siblings. It stops short of a crisp verb framing but the scope is clear.

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 enumeration of views (days, this-week, weekly-report, unlocks, build-market) implies what each mode is for, which is real routing help. However, there is no explicit when-to-use/when-not and no sibling is named as the alternative to reach for (e.g., get_project_timeline for per-project data). Usage is implied rather than stated.

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