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

Beyond annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true), the description adds key behavioral facts: it is x402-paid ($0.05) and intended as a pre-install safety check. It does not contradict annotations, and while it doesn't detail side effects like network calls, the payment disclosure is valuable. The tool's scoring nature is consistent with idempotentHint=true.

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, densely informative sentence: it leads with the tool's name and cost, states its action ('score'), the object ('MCP server manifest'), the condition ('before install'), the risk dimensions, and the output ('per-tool findings and fixes'). No filler or repetition.

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 13 parameters, an output schema, and a clear one-sentence purpose, the description covers the essential context. It mentions the output briefly, and the fact that it's paid is included. Slight room for improvement in giving a concrete example of the risk score, but overall it is complete for selecting and correctly invoking the tool.

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% with detailed parameter descriptions, so the baseline is 3. The description adds meaning by relating the input to MCP server manifests and risk categories (e.g., 'destructive tools' hints at the tools[].network and permissions fields), but it doesn't explicitly explain how to populate parameters beyond what the schema already offers.

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 clearly states the tool's specific purpose: 'score an MCP server manifest for security risk before install'. It enumerates what it checks (destructive tools, over-broad scopes, weak auth, egress) and the deliverable ('per-tool findings and fixes'), which distinguishes it from sibling tools like action_safety_quick_gate or walletguard_score that target different aspects of security.

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?

The description provides a clear context: use before installing an MCP server. It implies this is a pre-install assessment, separating it from tools that analyze runtime actions or payments. While it does not explicitly name alternatives, the specificity of 'MCP server manifest' gives strong guidance on when to invoke it.

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