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

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses the data provenance (daily fingerprints), the ordering, that by-design-changing servers are flagged, that results are signed, and the payment requirement ($0.01 USDC via x402 on Base or Solana). The cost/auth detail is exactly the kind of context an agent needs before invoking.

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?

Front-loads the core purpose and scope, then layers safety rationale, scope syntax, and pricing. Dense but every clause carries information; only the rug-pull aside could be trimmed.

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?

No output schema exists, yet the description covers scope, ordering, authentication/payment, and trust signals well enough to invoke it correctly. It is only slightly thin on what a returned change record contains.

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 0%, so the description must carry all three parameters, and it does map each one: days covers the 1-30 day window, name= and url= scope to one server. It doesn't clarify expected formats (registry name vs URL syntax), so it compensates well but not fully.

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+resource: reports tool changes (added, removed, redefined) across remote MCP servers in the Official MCP Registry, ordered newest first. This clearly separates it from mcp_server and mcp_top by content type, but it never explicitly names or contrasts a sibling, which is what a 5 requires.

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?

Gives concrete when-to-use context ('check before trusting a server again' because of rug-pull attacks) and the scoping conditions (last 1-30 days, or a single server via name=/url=). It stops short of naming an alternative or stating when-not to call it.

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