ssl_expiry_check

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

Discloses that expired certificates are included with negative days remaining and results are sorted. Annotations already indicate read-only idempotent behavior, and the description adds valuable behavioral details beyond them.

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 concise: three sentences and one Args line. Every part is meaningful and contributes to understanding, with no unnecessary words.

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, output schema exists), the description covers purpose, usage, behavior, and parameter semantics completely. It is fully self-contained for an agent to invoke correctly.

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 single parameter 'days' is explained in the Args section with its meaning and default value. With schema description coverage at 0%, the description fully compensates by adding clear semantics.

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 specifies a clear action: check SSL certificates expiring within N days. It states what is returned (name, expiry date, days remaining) and sorting order (soonest first), which distinguishes it from a general listing tool.

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 advises to use this tool instead of ssl_list when only certificates near expiry are needed. This provides a clear usage context, though no explicit when-not-to-use is given.

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