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

Annotations already provide readOnlyHint and openWorldHint, and the description adds 'No account required' and 'anonymous', confirming no side effects. This adds value beyond annotations, though it could detail potential rate limits or scan duration.

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 extremely concise, consisting of two sentences with no wasted words. It front-loads the key action and important traits (free, anonymous), making it easy to scan.

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 the rich annotations, 100% schema coverage, and existence of an output schema, the description adequately covers the tool's purpose and safety. It mentions returning certificate details, which is sufficient for a simple scan tool.

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 both parameters (domain and client_id) are already described in the input schema. The description adds no further parameter details, so it meets the baseline without additional value.

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 runs an SSL/TLS scan against a hostname and returns certificate details, with explicit indication that it's free and anonymous. The verb 'scan' and resource 'hostname' are specific, and the tool is easily distinguished from sibling tools which involve monitoring, certificate creation, or account management.

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 mentions 'No account required' and 'anonymous', suggesting it can be used without authentication for quick scans. However, it does not explicitly contrast with siblings like add_monitor for ongoing monitoring, leaving some ambiguity about when to choose this tool over others.

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