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

Annotations already declare readOnlyHint, idempotentHint, and closed-world behavior, so the safety profile is covered. Beyond that the description usefully enumerates what the returned playbook contains (objectives, techniques, detection signals, mitigations, pitfalls, references) and that target_context narrows results — meaningful content disclosure that annotations cannot convey.

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?

Two sentences, front-loaded with the core action and scope, then the playbook contents. No filler, no restatement of the title, and the optional-vs-required distinction is signaled immediately.

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 read-only retrieval tool with an output schema and full parameter documentation, the definition is nearly self-sufficient: it conveys scope, phases, and the role of target_context. The only gap is the absence of routing guidance against the six sibling tools, which matters given the high tool count.

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%, so vector, phase, and the nested target_context fields (waf, stack, recon_notes) are already fully documented with examples. The description only restates 'selected vector and optional target context' and adds the vector count; it contributes little syntax or format detail 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?

States a specific verb and resource — 'Return an authorized-testing methodology for a selected vector' — and scopes the output to a named set of 15 attack vectors. It is clearly distinguishable from siblings like pentest_generate_payloads or pentest_lookup_technique, which produce payloads or lookups rather than a multi-phase playbook.

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?

Usage is implied through the phase/vector scope and the 'authorized testing only' framing, but the description never states when to prefer this over pentest_lookup_technique or pentest_generate_payloads, despite the playbook apparently producing 'context-derived tool suggestions'. No explicit alternatives or exclusions are named.

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