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

The description says 'Run the scan,' implying a read-only action, and annotations confirm read-only and non-destructive behavior, but it does not call out side effects or limits beyond what annotations already state.

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 one long sentence with stylized bucket names and explanatory asides; it is informative but somewhat wordy, and the front-loaded purpose is somewhat buried by the extended categorization.

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 explains the output buckets and their significance, and with the output schema present it gives enough context for an agent to know what to expect from a call.

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, domain, is documented in the schema with a clear example. The description adds no further detail about the parameter, so it relies on 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 clearly specifies the tool's purpose: it runs a scan and sorts failed checks into prioritized buckets, with category examples. This distinguishes it from sibling scan/visibility tools by emphasizing prioritization.

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 describes what the tool does but does not explicitly state when to choose it over the sibling scan or visibility tools; no direct when-to-use guidance is provided.

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