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

Discloses that the tool is free, returns a subset of checks, results are unsigned and not stored, and is compliance aid not legal advice. Adds value beyond annotations (readOnlyHint, idempotentHint) by specifying behavioral traits.

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 sentences, front-loaded with purpose and key details. Every sentence adds value with no redundancy or fluff.

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 simple tool with one parameter and no output schema, the description covers purpose, scope, behavioral traits, and limitations. Lacks error handling or response format, but acceptable for a quick-scan 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 a well-described 'url' parameter. Description adds no additional parameter-level details, but provides context about the scan scope. Baseline 3 is appropriate as schema does the job.

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?

Clearly states the tool performs a free compliance and security quick-scan on a public web URL, listing specific checks. Distinguishes from sibling tools like scan_app and get_compliance_rules by focusing on quick-scan functionality.

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?

Implies usage for quick checks versus a full scan requiring an account. Notes that the result is unsigned and not stored, guiding expectations. Does not explicitly contrast with all siblings, but provides context for when to use this free offering.

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