Analyze HTTP security headers

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, but the description adds the crucial constraint that no HTTP request is performed, which is not captured by annotations. This provides valuable context beyond the structured metadata.

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, front-loaded sentence with no filler words. Every word adds meaning, and it perfectly integrates the core purpose with the key behavioral nuance.

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 tool's simplicity and the presence of an output schema, the description covers the high-level behavior well. However, with three required parameters and zero schema descriptions, the missing parameter semantics create a notable gap. An agent would struggle to correctly populate 'target' and 'engagement_id' without additional information.

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 0%, and the description does not explain the parameters 'engagement_id', 'target', or 'headers'. While 'headers' is implied by the description, 'target' and 'engagement_id' are completely undocumented, leaving the agent to guess their purpose. The description fails to compensate for the lack of schema-level descriptions.

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 uses a specific verb ('Analyze') with a clear resource ('caller-supplied response headers') and adds the key differentiator 'offline; no HTTP request is performed.' This distinguishes it from sibling tools like scan_repository, which likely performs live requests.

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 clearly implies use cases by emphasizing that analysis is performed offline with caller-supplied data, so an agent understands this is for inspecting existing headers rather than fetching them. However, it does not explicitly name alternatives or provide exclusion criteria, so it falls short of a 5.

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