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

No annotations are provided, so the description carries the behavioral burden. It discloses the single-URL limitation, which is useful, but doesn't describe whether the tool follows redirects, whether it checks live or cached headers, or what happens on connection failure. The main behavioral trait (single-URL constraint) is disclosed, but richer detail would be needed for a thorough pass.

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?

Exactly two sentences: the first states the core function and the single-URL constraint; the second names alternatives for broader scans. No filler or redundant phrasing.

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 one parameter, no output schema, and no annotations. The description captures the essential purpose, scope limitation, and alternative routes for adjacent needs. It lacks details about return shape or failure behavior, but for a simple single-parameter inspection tool, the coverage is quite good.

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 schema only lists 'url' as a string with no description. The description compensates by clarifying that the URL must be a single URL and specifically for HTTP security headers. It doesn't state URL format requirements, but with only one parameter and no schema guidance, the description adds meaningful clarity.

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 states a specific verb ('Inspect'), resource ('HTTP security headers'), and clear scope ('for ONE URL only'). This distinguishes it from broader audit/posture tools and sibling tools like get_ssl_check or get_dns_lookup.

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 explicitly says this tool is for one URL only and routes to use /web/audit or /security/posture for headers combined with TLS/DNS. It doesn't enumerate exclusions vs all siblings, but the single-URL constraint and alternative routing are clear and actionable.

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