tls_certificate

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

No annotations are present, and the description provides minimal behavioral context. It implies a read-only operation ('check'), but does not disclose potential blocking, rate limits, error conditions, or the depth of security analysis. The description leaves the agent uninformed about side effects or limitations.

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 (two sentences) and front-loaded with a clear purpose. However, its brevity sacrifices necessary detail, making it under-specified rather than efficiently concise. Every sentence earns its place, but there are too few sentences to be fully effective.

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 simplicity (one parameter, no output schema, no annotations), the description is incomplete. It does not describe the return format, specific details returned (e.g., expiration, issuer), or what constitutes 'security' checks. More information is needed for an agent to reliably invoke and interpret results.

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 0%, and the description only offers an example ('example.com') for the required 'domain' parameter. It does not explain the expected format (e.g., protocol prefix, IP addresses) or any constraints. The description fails to compensate for the lack of schema documentation.

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 states 'Check TLS certificate details and security' with an example, clearly indicating the tool's function of inspecting TLS certificates. It differentiates from siblings like whois_info or dns_records by focusing on certificate-level inspection, though the scope of 'security' is vague.

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 explicit guidance on when to use this tool versus alternatives. Only an example is provided, implying usage for a given domain, but no criteria or exclusions are mentioned.

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