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

Annotations already declare the operation is read-only and idempotent, and the description adds valuable behavioral detail beyond that: it operates only on public metadata, makes no network calls, requires no auth, and does not inspect source code or certify vulnerabilities. No contradiction with annotations.

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?

Two tight sentences: the first states the core function and source, the second gives usage timing and explicit non-behaviors. Every clause earns its place and the most decision-relevant information is front-loaded.

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?

The description covers purpose, usage context, and behavioral constraints, and an output schema exists so return values need not be spelled out. The only notable gap is the undocumented nested input object, which weakens invocation readiness but not tool selection.

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 description coverage is 0%, so the description carries the burden for explaining inputs, but it only loosely references 'tool descriptors, schemas, and registry claims.' It never explains the required `risk_scan` object or its nested fields, leaving the agent to infer meaning from property names alone.

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 verb ('Return'), a concrete resource ('MCP risk score'), and the data sources ('tool descriptors, schemas, and registry claims'). It clearly distinguishes this from the sibling tools by framing it as a read-only metadata-based risk score.

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 explicitly says when to use it ('Before listing, integrating, or wrapping another MCP server') and provides concrete exclusions ('does not fetch network data, require auth, mutate systems, inspect source code, or certify vulnerability status'). This gives an agent clear go/no-go guidance even without naming an alternative tool.

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