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

readOnlyHint=true already covers safety. The description spends its words on the project's prior-art framing ('we did not invent it', '0 USD earned') rather than tool behavior such as what the response contains or its format. It does disclose that the response begins with prior art, but not enough about the tool itself.

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?

Rambling prose with a manifesto tone ('WHY THIS EXISTS, and what it does not claim') rather than a front-loaded functional statement. Several sentences on prior art and honesty metrics don't help an agent invoke the tool.

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 no-param read tool the description is long but omits the essentials an agent needs: what exactly is returned beyond 'prior art, the one property, honest numbers', and how it differs from siblings like project100_info. The rich adjacent toolset makes this omission costly.

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?

Zero parameters, so baseline 4 applies. No parameter information is needed or missing.

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 name and title suggest a 'vision' statement; the text describes a work record recomputable without trusting the issuer, but the actual operation (retrieving a vision/manifesto document) is only implied. It's clearer than a tautology but not a specific verb+resource statement.

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?

There's a 'read this before deciding whether the record is worth anything' framing, but no explicit when-to-use/when-not guidance and no reference to any of the many sibling tools. An agent cannot tell from this why to call vision vs project100_info or project100_coin_whitepaper.

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