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

With no annotations, the description carries the full burden of behavioral disclosure, but it only lists output fields and the word 'Live'. It does not state how the lookup is performed, what input is expected, whether network access is needed, or any caveats, leaving the agent without important 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?

The description is compact and front-loads the core concept followed by the relevant output fields, with no filler. However, it is a noun phrase rather than a complete instruction, so the structure is minimally adequate but not exemplary.

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 tool with no annotations, no parameter documentation, and a single loosely described q parameter, the description leaves too much unspecified for an agent to invoke it confidently. The presence of an output schema helps with return values but not with input semantics or selection context.

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 q has no schema description, and schema description coverage is 0%. The phrase 'TLS Certificate' provides some context that q is probably a hostname or domain, but the description never explicitly defines q or its expected format, so the agent must guess.

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 identifies the resource (TLS certificate) and the nature of the data (live certificate with issuer, validity, SANs, and cipher), so an agent can infer this tool retrieves current TLS certificate details. It falls short of a 5 because it lacks an explicit verb like 'retrieve' and does not explicitly distinguish itself from siblings such as tlsscan or tlsa.

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?

There is no guidance about when to use this tool instead of certificate-related siblings like tlsscan, tlsa, or certhistory, and no mention of prerequisites or exclusions. The word 'Live' weakly implies current-state usage, but that is not enough for an agent to reliably decide between alternatives.

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