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

Annotations already establish readOnlyHint=true and idempotentHint=true, so the agent knows this is a non-mutating, repeatable operation. The description adds value by disclosing that the returned content is an 'authorized-testing' playbook that covers phases (recon, enumeration, exploitation, post_exploitation) and includes elements like detection signals, mitigations, and 'context-derived tool suggestions.' This goes beyond the annotations by describing the nature of the output without contradicting them.

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, information-dense sentence that front-loads the core action and resource, then enumerates the coverage without redundancy. Every phrase contributes (phases, objectives, techniques, detection signals, mitigations, pitfalls, references, tool suggestions). It is compact yet comprehensive, making efficient use of the word budget.

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 that an output schema exists (as indicated), the description does not need to explain return formats. The description covers all key aspects: the action, the resource, the scope (15 vectors), optional narrowing, and the content of the playbook. For a read-only, idempotent tool with full schema coverage, this is complete. An agent has enough information to invoke it correctly without ambiguity.

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 input schema provides full coverage (100%) for all three parameters, including enums and descriptions for vector and phase, and property-level descriptions for the target_context object. The description simply restates the existence of a 'selected vector' and 'optional target context,' adding no new meaning beyond the schema. Given the high schema coverage, a baseline of 3 is appropriate; the description does not compensate or enrich parameter semantics.

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 states the tool's function: 'Return an authorized-testing methodology for a selected vector and optional target context.' It identifies the specific resource (methodology) and the action (return), and specifies that it covers a full set of phases. This clearly distinguishes it from sibling tools like pentest_generate_payloads or pentest_analyze_response, which have narrowly scoped purposes.

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?

The description implies its usage context: it is for retrieving a methodology for a vector, optionally narrowed by target context. However, it does not explicitly state when to prefer this tool over its siblings, nor does it name any alternatives. There is no 'when-not-to-use' guidance or comparison to pentest_map_techniques or pentest_lookup_technique. The usage context is inferable but not explicit, so it falls short of a 4.

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