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

Annotations already cover safety (readOnlyHint) and open-world scope, so the description correctly spends its budget elsewhere: it discloses measurement boundaries ('distinct caller addresses per day — addresses, not people'), freshness, 'what HEY does not know', and why data may be withheld. These are genuine behavioral caveats an agent cannot get from the structured fields.

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 opening clause is well front-loaded, but the remainder is a dense recursive inventory of return-field domains ('context blocks, never building: paid promotion…, DefiLlama protocol economics…, developer footprint…') that reads like a spec dump. For a selection decision, most of these phrases do not change whether an agent picks this tool, so much of the length is not earning its place.

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?

There is no output schema, so the description must carry return-shape information — and it does so thoroughly, covering each context block and even the absence cases. Given the breadth of the snapshot, this is close to complete; only ordering/pagination-style details are absent, and those appear unnecessary for a single-project read.

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?

Only one parameter (slug) with 100% schema description coverage including an example, so the schema already does the work. The description adds no syntax, format, or resolution guidance beyond it, which is acceptable at this coverage level.

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 a specific verb and resource — 'everything important about one project in one read' — and enumerates the domains covered (identity, build status, market context, on-chain use, product usage, verification, locks, changes). It does not name any sibling tool, so the agent must infer its boundary against get_project_timeline, ask_hey, or get_project_coverage on its own.

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 closing clause 'Use this first for "tell me about X"' is a real usage cue and implies precedence over conversational siblings, but no explicit alternatives or when-not conditions are named. With fourteen siblings, the routing burden falls almost entirely on that one sentence.

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