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

No annotations are provided, so the description carries the behavioral disclosure burden. It does disclose the output transformation behavior (score/grade/findings instead of raw fields) and narrows the target to public HTTPS sites, but it does not mention whether this involves a live scan, potential latency, failure behavior, or any rate/usage constraints.

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 entire description is one compact sentence that front-loads the purpose, identifies the inspection scope, names the sibling alternative, and states the key output difference. Every clause contributes meaning with no repetition or filler.

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 simple one-parameter GET-style tool without an output schema, the description is largely sufficient: it states what is assessed, the output format, and the relationship to a sibling tool. It could be more complete with an explicit usage recommendation and a bit more detail about the returned findings, but nothing essential is missing for basic invocation.

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 input schema only defines 'url' as a required string with 0% description coverage, so the description must compensate. It adds the key semantic that the URL should be a public HTTPS website, but it does not specify URL format details or whether the scheme must be explicit, leaving some ambiguity for a single-parameter tool.

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 uses a specific verb ('Assess'), names the exact resource (TLS and HTTP security posture for a public HTTPS website), and distinguishes itself from the sibling get_web_audit by clarifying it returns a score/grade/findings rather than raw fields. It clearly differentiates the tool within the sibling set.

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 points to the same inspection as /web/audit, which identifies get_web_audit as the alternative, and implies the choice depends on whether the caller wants a summarized score/grade/findings versus raw fields. It provides clear context but does not explicitly state when to choose one over the other or give exclusions.

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