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

With no annotations, the description carries the full burden and it partially delivers by enumerating the returned content (totals, positions, per-ecosystem tags). But it does not disclose behavioral traits such as read-only nature, data freshness/snapshot timing, cost, or rate limits, and references to 'the harvester' are unexplained.

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 content is front-loaded with the core figure described first, but the main sentence is a dense run-on that stacks specialized terms (harvester, handshake-ready, TEE claims, work surfaces) without definition. It is information-dense but not wasteful; readability suffers slightly.

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 convey what is returned, and it does list chains with agents and counts, work surfaces, TEE claims, unscanned chains with reasons, totals, positions, and per-ecosystem tags. This is reasonably complete for a read-only overview surface, though freshness and format specifics are absent.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate, and the empty schema with additionalProperties=false is self-consistent. Baseline for a zero-parameter tool is a 4.

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 states a clear resource and scope: a single-figure overview of every agent ecosystem the harvester has read, including per-chain agents, handshake-ready counts, work surfaces, TEE claims, and unscanned chains. It does not name a crisp verb, but the 'landscape' framing and content list make its purpose unambiguous. It lightly distinguishes itself by positioning against hire/register, though it does not directly name sibling tools.

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?

It gives some context: 'Read this to know where agents are before you hire or register,' which implies a discovery/pre-flight use. However it offers no explicit exclusions, no pointing to a specific alternative tool, and no conditions under which you should skip it.

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