scan_ssl_certificate

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

With no annotations, the description correctly highlights the tool is read-only and non-modifying, which is critical. However, it does not disclose other behavioral traits such as rate limits, prerequisites, or error handling.

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 two sentences long with no redundant information, efficiently conveying purpose and safety.

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 has one optional parameter and no output schema, the description covers the essential purpose and safety. It is adequate for a simple scanner, though it could hint at what the scan produces.

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 description adds value beyond the schema by noting the default behavior ('default: server region') for the region parameter, which is not present in the schema itself.

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 states 'Run SSL Certificate security scanner only', specifying the action and resource. It distinguishes from sibling tools by emphasizing read-only nature and non-modification of AWS resources.

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?

The description implies it is safe for read-only SSL scanning but does not explicitly state when to use vs alternatives like scan_all or other scanners. No alternatives or when-not-to-use guidance is provided.

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