SSL Live Chain Lookup

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds behavioral details: what certificates included, fields per cert (chain order, validity, subject/issuer, public key, key usages, SAN, PEM). No contradictions. Could mention rate limits or caching, but adds good context.

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?

Three sentences, front-loaded with purpose, lists contents, provides alternative. No fluff. Every sentence serves a clear function.

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?

No output schema, so description must detail return values. It lists all expected fields (chain order, validity, subject/issuer, public key, key usages, SAN, PEM). Mentions 'when available' for intermediate/root. Lacks mention of response format (JSON likely), but sufficiently complete for a certificate chain 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%, so baseline is 3. Description does not elaborate on parameters beyond mentioning 'domain' implicitly. The optional ssl_raw parameter is not described in text. Schema descriptions suffice, but description adds no extra parameter meaning.

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?

Description uses specific verb 'Retrieve' and resource 'complete live SSL certificate chain'. It lists exact contents (leaf, intermediate, root) and explicitly distinguishes from sibling 'ssl_live_lookup', which retrieves only the end-user certificate. No ambiguity.

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?

Explicitly states when to use this tool vs. alternative: 'To retrieve only the end-user certificate, use 'ssl_live_lookup' instead.' Provides clear context and exclusion.

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