check_security_headers

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

With no annotations, the description bears the burden of behavioral disclosure. It discloses that the tool performs an active GET and requires a specific permission, which is useful. However, it does not mention potential side effects, failure modes, rate limits, or what exactly happens when the URL is unreachable. The description gives partial transparency.

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 sentence that efficiently conveys the tool's function, the required permission, and the checks performed. No fluff, and the core purpose is front-loaded. Every word earns its place.

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 lists the categories of findings (missing headers, version disclosure, etc.), which gives a reasonable idea of the output. However, it does not specify the return format, success/error behavior, or how results are presented, leaving some gaps for an agent.

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%, so the description must compensate. It clarifies that the 'url' parameter is the URL to fetch from the hub, but adds little beyond that. It does not explain URL format expectations, restrictions, or how the URL relates to the hub. Minimal semantic value added.

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 a specific action: GET a URL and report missing security headers, version disclosure, cookie flags, and HTTP->HTTPS redirect. This is a specific verb and resource with concrete checks. However, it does not explicitly distinguish itself from security-related siblings like security_posture or get_tls_status, so it stops short of a 5.

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 given on when to use this tool versus alternatives. The only added note is the permission requirement (DIAG_ALLOW_ACTIVE_CHECKS), which is a prerequisite, not a usage signal. There is no mention of when this check is appropriate compared to passive checks or other security tools.

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