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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the agent knows this is a safe, non-mutating operation. The description adds value by disclosing what the tool produces: structured findings covering specific categories (version disclosures, stack traces, debug headers, internal paths, authentication patterns, CORS configuration, detection signals, remediation, and methodology vectors). This goes beyond the annotations by describing the output structure and scope. No contradiction with annotations.

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, dense paragraph that front-loads the core purpose ('Analyze an HTTP response from authorized probing') and then lists the finding categories. It's efficient with no filler words. The list of categories is somewhat long but each item adds value by clarifying the tool's scope. Could be slightly more structured (e.g., bullet points) but is acceptable as prose.

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 tool has an output schema (not shown in detail but indicated by 'Has output schema: true'), which likely describes the structured findings. The description covers the input parameters (via schema) and the output categories. The description mentions 'remediation' and 'methodology vectors' which are important for a pentest tool. Given the complexity of a security analysis tool, the description is reasonably complete. It could mention that the tool is read-only (though annotations cover that) or provide more detail on how the analysis works, but the current level is adequate.

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 all four parameters (context, status_code, response_body, response_headers) are already well-documented in the schema. The description doesn't add parameter-specific semantics beyond what the schema provides. The description mentions 'context' narrows pattern matching, which aligns with the schema's description, but doesn't add new information. Baseline 3 is appropriate given full 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 clearly states the tool's purpose: analyzing HTTP responses from authorized probing for information leakage, fingerprinting signals, and related exposure. It lists specific categories of findings (version disclosures, stack traces, debug headers, etc.), which distinguishes it from sibling tools like pentest_generate_payloads or pentest_map_techniques. The verb 'analyze' and resource 'HTTP response' are specific and unambiguous.

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 usage context: it's for analyzing responses from authorized probing, which suggests it should be used after sending requests. It doesn't explicitly state when not to use it or name alternatives, but the sibling tools are clearly different in function (encoding, payload generation, lookup, mapping). The 'authorized probing' qualifier provides important usage context. However, it doesn't explicitly say 'use this when you have a response to analyze' or contrast with alternatives.

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