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

Annotations already declare this as a read-only, idempotent operation, so the description does not need to repeat safety traits. It adds useful behavioral context by explaining the output includes relevance, detection opportunities, mitigations, and methodology vectors, though some of this is redundant with the existing output schema. It does not clarify whether this is a local knowledge-base ranking rather than a live scan, but the 'authorized target profile' framing partially signals a planning-oriented operation.

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 two sentences with no filler, front-loading the verb, resource, and target context. The phrase 'associated methodology vectors' is somewhat vague and imprecise, which keeps it from being perfectly concise, but overall every sentence earns its place.

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 the output schema exists and input schema fully documents parameters, the description covers the essential invocation context well. It does not mention behavior when no profile parameters are provided, but because all parameters are optional and the schema documents defaults, this is a minor omission rather than a critical gap.

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 description coverage is 100%, and the schema already documents every parameter including defaults and enum constraints. The description restates four of the five profile dimensions (stack, services, auth_type, os) but adds no new semantic detail beyond what the schema provides, matching the baseline for high schema coverage.

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 names a specific verb ('Rank') and a precise resource ('ATT&CK techniques and OWASP test cases'), then scopes it to a target profile composed of concrete dimensions. This clearly separates it from siblings like pentest_lookup_technique and pentest_generate_payloads by indicating a multi-technique prioritization operation rather than a single lookup or payload construction.

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 provides clear situational context: use when you need profile-specific ranking of attack techniques and test cases against a target's stack, services, auth type, and OS. It does not explicitly name alternatives or state when not to use it, but the described use case is unambiguous enough for an agent to select it correctly.

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