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

Annotations already establish that this is a safe, idempotent read. The description adds genuinely new context — the endpoint path and the $0.01 price, which signals a paid call — but it never mentions the 402 challenge/retry flow that actually governs invocation; that only appears in the payment parameter's schema text.

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 short fragments, no filler, with the resource description front-loaded ahead of the route and price. Terseness is the only concern; nothing is redundant.

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 one required parameter, full schema coverage, and read-only annotations, the essentials are covered. However, with no output schema the description should say more about what the policy matrix contains or its shape, and it never acknowledges the payment handshake that a first call will trigger.

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 100%, so both host and the payment-proof parameter are already fully documented in the schema, including the omit-on-first-call behavior. The description adds only the price, leaving the baseline 3 appropriate.

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 names the concrete deliverable — a TLS/security-headers/AI-crawler policy matrix for a given host — plus the exact route, so an agent knows what it will get back. It stops short of distinguishing itself from the sibling check_security_headers, whose scope visibly overlaps.

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?

There is no statement of when to reach for this tool versus check_security_headers or check_webmcp, and no preconditions are given. The agent must infer the use case from the resource name alone.

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