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

With no annotations, the description carries the full burden. It usefully discloses cost ('FREE') and implies a passive read-only directory with no side effects, but says nothing about authentication requirements, rate limits, or whether the returned catalog is static or live. Adequate but thin for an unannotated tool.

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 dense sentence with the most decision-relevant token ('FREE') front-loaded, followed by the content inventory. Efficient, though the parenthetical alias list is long and could be trimmed without loss.

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 zero-param, no-output-schema info tool, the description is nearly complete: it tells the agent exactly what categories of information the call returns, so no follow-up is needed to decide whether to invoke it. Only the absence of any usage routing keeps it from being fully complete.

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 per the rubric the baseline is 4. There is no parameter semantics to explain, and the description correctly does not invent any.

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 names a specific resource (service directory for the On-chain Forensics MCP server) and enumerates its contents: endpoint catalog, supported chains, pricing, tokenized-equity aliases, and usage examples. That is clearly distinct from the sibling tools (diligence_memo, settle_safe, token_profile, token_verdict, wallet_screen), though it never explicitly contrasts itself with them.

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?

'FREE' implies this is the no-cost entry point for discovery before calling paid siblings, which gives an implied usage context. However, there is no explicit when-to-use statement, no prerequisites, and no named alternatives, so the agent must infer the routing on its own.

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