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

With no annotations, the description fully discloses behavioral traits: it returns only issue count, severity breakdown, risk score, and verdict, but NOT which tools or evidence. Also mentions it's free and requires no payment, implying no destructive side effects.

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?

Four concise sentences, each adding value: purpose, return details, limitations, and usage guidance. No redundant information. Front-loaded with the core action.

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?

Given a single parameter and no output schema, the description covers all necessary information: what the tool does, what it returns (and does not return), and when to use the paid sibling. Fully adequate for correct invocation.

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?

Only one parameter 'url' with 100% schema coverage. The description adds minimal context beyond the schema (e.g., 'free preview-scan'), but the schema itself is clear. Baseline 3 is appropriate as the parameter semantics are already well-defined.

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?

Explicitly states it's a free preview scan for tool-poisoning/prompt-injection on MCP servers. Clearly distinguishes from the paid scan_mcp_server sibling by specifying it returns only summary stats, not detailed findings.

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?

Provides explicit guidance: use this free preview first; if issues found, call paid scan_mcp_server for itemized findings and remediation. This clarifies when to use this tool vs the paid alternative.

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