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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only names the vulnerability types being checked but does not say whether live requests are made, how results are returned, or what caveats apply to the scan.

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 compact and the 'Origin-reflection / wildcard misconfig' part adds value beyond the title. However, it is so terse that it borders on under-specification rather than efficient completeness.

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 one-parameter scanning tool, the description lacks input semantics, usage guidance, and output interpretation. The output schema helps, but the description does not connect the parameter to the behavior, leaving the agent to guess what `q` should contain.

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?

The schema has a single undocumented parameter `q` with 0% description coverage, and the tool description never mentions `q` or what value it expects (URL, domain, hostname). An agent cannot reliably construct a correct invocation from the available information.

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 identifies CORS as the resource and names the specific misconfigurations checked (origin-reflection / wildcard). 'Check' acts as the verb, and the focus on CORS distinguishes it from unrelated security siblings, though it could more explicitly state it evaluates a user-supplied URL.

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?

There is no guidance on when to use this tool versus alternatives like headers, httpmethods, or clickjacking. No context is given for prerequisites, target format, or situations where this check would be inappropriate.

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