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

The description does disclose payment behavior (unpaid calls return PAYMENT-REQUIRED) and provides a default body, which hints at request behavior. However, it does not disclose what happens on success, whether the operation is read-only, or any side effects, leaving the actual scan behavior opaque.

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?

The description is a single run-on paragraph mixing pricing, endpoint, default body, and payment notes, making it cluttered and hard to scan. It lacks a clear front-loaded purpose statement and reads more like a billing spec than an API tool description.

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 there is no output schema, the description should explain what the tool returns or how to interpret the response, but it does not. It also omits any context about the actual scanning logic, prerequisites, or expected outcomes, leaving the tool functionally underspecified.

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 each parameter having a description, and the default body provides a concrete example of nested fields. Nonetheless, the body description is generic ('JSON POST body for the intel/security route') and does not explain each inner field, so it adds only marginal meaning beyond the schema.

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 never states what the tool actually does—it only gives an endpoint, payment details, and a default JSON body. The name 'security-deep-scan' implies a function, but no explicit verb or resource outcome is described, making it nearly tautological.

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?

No guidance is given about when to use this tool versus its siblings like security_scan or security_readiness. There is no mention of use cases, prerequisites, or selection criteria.

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