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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds operationally useful context beyond that: it performs a live GET, does not follow redirects (a real behavioral trait that affects results), and is free of charge. It doesn't describe output shape, but that is minor given the explicit header list.

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?

Two tight sentences: the operation and covered headers are front-loaded, followed by operational constraints and cost. No filler or redundancy.

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 single-parameter read-only audit with no output schema, the description supplies the essentials: what is fetched, what is evaluated, and the no-redirect behavior. The absence of any note on return format or result granularity is the only gap, and the header enumeration largely compensates.

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 100% and the single 'url' parameter is fully documented as 'Domain or https URL'. The description adds a marginal constraint (HTTPS only), but otherwise the schema carries the parameter explanation, so baseline 3 applies.

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?

States a specific verb (audit) and resource (HTTP security headers), and enumerates exactly which headers are checked (HSTS, CSP, X-Content-Type-Options, frame protection, Referrer-Policy, Permissions-Policy). This clearly distinguishes it from siblings like bursia_tls_certificate and bursia_dns_records without needing to open any schema.

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?

Sets clear preconditions for use: the target must be a public HTTPS page, and it clarifies that no redirects are followed. It stops short of naming alternatives or exclusions (e.g., 'use tls_certificate for certificate chain issues'), so the agent must infer sibling routing.

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