fingerprint_headers

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

There are no annotations, so the description carries the full burden. It only states 'Analyze security headers,' which implies a read-only inspection but does not disclose whether it makes network requests, what output to expect, potential side effects, or any permissions needed. This is a minimal but not entirely empty disclosure.

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 concise sentence with no wasteful words. It is easy to read and front-loads the core action, though its brevity leaves out important details.

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?

With only one parameter, no output schema, and no annotations, the description is far too sparse to give an agent adequate understanding of the tool's behavior, return values, or interpretation of results. It does not enable reliable invocation or use.

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 coverage is 0% and the description provides no parameter semantics. The single parameter 'url' has no description, and the tool description does not explain what should go in it, what format is expected, or any constraints. The description fails to compensate for the lack of schema documentation.

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 identifies the resource ('security headers') and the action ('analyze'), which distinguishes it from sibling tools like fingerprint_url and fingerprint_waf. However, 'analyze' is somewhat generic and doesn't specify the nature of the analysis beyond that resource.

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?

No guidance is provided on when to use this tool versus alternatives. It neither names alternatives nor gives examples of suitable use cases or exclusions, leaving the agent without decision support.

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