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

Annotations already cover the read-only, closed-world safety profile, so the description's job is output shape — and it delivers: it discloses that each investor carries only the first 20 funded projects, that projects_more counts the remainder, and that pages hold 50 records. It omits data freshness and per-investor fields, but the added context is meaningful.

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?

A single front-loaded sentence with the resource and ranking first, then the output-shape caveats, then attribution. The nested parenthetical is dense but every clause carries information; no filler.

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 must explain what comes back, and it covers ranking field, record count per page, and the truncation semantics via projects_more. What is still missing is the actual set of fields per investor (name, avatar, socials, amounts) and whether the top-100 boundary interacts with paging.

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 100%, and the description largely restates what the schema already says about page size and the two sort modes. The projects_more note adds value but relates to output, not to the two input parameters, so baseline 3 is right.

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 resource and scope: the top 100 crypto investors, ranked by projects funded or USD invested. An agent can immediately tell this is a leaderboard listing rather than a lookup. It does not explicitly name the nearest sibling (investor_profile), so differentiation is only implicit.

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?

Usage is implied — this is the browsing/ranking tool — but the description never says when to use it over investor_profile or project_funding, nor any prerequisites. No exclusions or alternatives are given.

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