http_headers_audit

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

With no annotations provided, the description carries the burden of behavioral disclosure. It explains the connection context (port defaults based on use_ssl, timeout), the scope of inspection, and the return structure. It stops short of describing failure modes or redirect handling, but for a read-only audit tool the behavioral picture is solid.

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 structured with a clear opening, a list of inspected headers, and separate Args/Returns sections. Every sentence adds useful information; the header enumeration is purposeful, and there is no filler or repetition of schema fields.

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 tool with no annotations and no output schema, the description is remarkably complete: it covers all four parameters, explains defaults and dependencies, and specifies the returned structure. An agent has enough to invoke the tool correctly and interpret the result.

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 has 0% description coverage, so the description is the only source of parameter meaning. It fully compensates by explaining each argument, including the port default behavior tied to use_ssl and the timeout as a per-connection value in seconds. This goes well beyond what the raw schema provides.

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 opens with a specific verb and resource: 'Audit a web server's HTTP security response headers and grade them.' It lists the exact header families inspected and names a concrete outcome (letter grade plus findings), which clearly distinguishes it from sibling tools like cookie_audit, http_methods_audit, and tls_check.

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 makes the tool's purpose clear and implies its use case, but it never explicitly states when to choose this tool over sibling alternatives such as cookie_audit or well_known_audit, nor does it give any exclusions. Context is present, but alternative routing is left to inference.

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