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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds valuable context such as 'Everything is read from the public internet: nothing is authenticated, no ports are scanned, and no credentials are needed,' which clarifies the tool's non-intrusive behavior and pricing model. No contradiction with annotations.

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 longer than average but every sentence provides distinct value: purpose, use cases, coverage details, access method, exclusions, alternative, and pricing. It is front-loaded with the core purpose and avoids filler, though slightly dense.

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?

Given that an output schema exists and the tool has modest complexity (one parameter), the description covers all necessary context: what it measures, when to use it, safety profile, exclusions, and how it differs from the sibling. Nothing is missing.

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?

The schema already fully describes the single 'domain' parameter with examples and constraints, achieving 100% coverage. The description reinforces the public-only scope but does not add new parameter-level details, so baseline 3 is 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 opens with a specific verb and resource: 'Measures how resilient a public web domain is from the outside' and clearly lists outputs (weighted score out of 100, per-category breakdown, prioritised findings). It also distinguishes itself from the sibling tool by noting 'domain_check_score_v1' provides a free score without detailed findings.

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?

Explicit use cases are given: 'audit a domain you do not control, verify a fix after deployment, or compare several domains.' It also states exclusions ('Do not use it for private, internal, or localhost hostnames, for IP addresses...') and points to an alternative tool for a simpler score. This is comprehensive guidance.

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