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

With no annotations provided, the description carries the burden of behavioral disclosure. It does reveal a key behavior: output is raw findings and no score is computed. It also indicates the audit is a combination of DNS, TLS, and HTTP checks. However, it does not mention authentication requirements, rate limits, or the exact structure of the findings, which are relevant for a security audit tool.

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 two sentences with no fluff. It front-loads the core purpose, clearly states the output style, and includes an alternative in a compact way. 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 combines multiple audit areas and there is no output schema, so the description should provide more context about what the raw findings include or how they are structured. It does mention the components (DNS, TLS, HTTP headers) and the no-score nature, but lacks details on the response format, error behavior, or required URL validation rules. Given the moderate complexity, this is acceptable but not complete.

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 has a single 'url' parameter with zero description coverage. The tool description only mentions 'a public HTTPS website,' which hints at the expected input type but does not clarify URL format, protocol requirements, or how the parameter is used in the audit. Given the low coverage, the description should compensate more explicitly, but it does not.

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 the tool performs a consolidated DNS, TLS, and HTTP security audit for a public HTTPS website, and specifies it returns raw findings without a score. It also explicitly differentiates itself from sibling tools by identifying it as the bundled version of three separate endpoints, so an agent knows exactly what resource this tool covers.

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 provides a clear alternative: 'Use /security/posture instead for a 0-100 score/grade.' This tells the agent when to choose a different tool if a score is desired. However, it does not elaborate on specific scenarios where the bundled audit is preferable over individual lookups beyond the implicit 'bundled' nature, leaving some room for inference.

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