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

Beyond readOnlyHint and idempotentHint, the description explains nuanced behavior: invalid certs are delivered as valid=false + validation_errors[] rather than failures, and clarifies the grading semantics (D vs F). This gives operational insight annotations alone cannot convey.

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 dense but well-structured: purpose, edge-case behavior, grading definition, usage note, rate limit, and return format. While every sentence adds value, it is slightly longer than strictly necessary; a tighter rendition could push it to 5.

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 tool's single simple parameter and the presence of an output schema, the description covers all essential operational aspects: what it returns, how invalid certs are handled, the meaning of grades, and when to use it. Nothing important is omitted.

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 only parameter, domain, is fully described in the schema (100% coverage) with examples. The description adds no additional parameter-level semantics beyond what the schema already states, so the baseline of 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 'Analyze SSL/TLS certificate', a specific verb+resource, and lists concrete outputs (grade, protocol, cipher, etc.). It distinguishes itself from sibling tool audit_domain by explicitly noting 'for full domain audit use audit_domain'.

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?

Provides explicit when-to-use guidance: 'Use to audit certificate validity and detect expiring certs', and explicitly points to an alternative tool for broader audits. Also includes practical rate limit context (Free 30/hr, Pro 500/hr).

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