check_ssl_certificate

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only mentions cost and category, with no mention of network calls, input expectations, or output structure, providing essentially no behavioral transparency.

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 very short but under-specified; it does not efficiently cover necessary information. It consists of a restated name and a cost note, failing to use the space to convey tool functionality.

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?

There is no output schema, and the description provides only a title-like phrase and a price. An agent cannot determine how to invoke the tool, what arguments to provide, or what results to expect, making it contextually incomplete.

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's only parameter is a generic 'params' object with a placeholder description ('Tool parameters as JSON object'), giving no real meaning about required inputs. The description does not compensate by mentioning expected inputs like a domain name or URL, making parameter semantics effectively absent.

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 restates the tool name verbatim ('check ssl certificate') and adds only a generic category label ('Security & Network tool'). It doesn't specify what the tool actually does (e.g., validity, expiry, issuer) or distinguish it from sibling tools like ssl_chain_check.

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?

No guidance is provided on when to use this tool versus alternatives. The description never mentions context, prerequisites, or exclusions, leaving the agent without any selection rationale.

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