get_expiring_certs

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

No annotations are provided, so the description carries the full burden. It states it returns certs expiring within days but does not disclose if it includes already expired certs, the response format, or whether it is read-only. Minimal behavioral context beyond purpose.

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 a single sentence with no filler words, achieving conciseness. However, it could be structured to include parameter details without losing brevity.

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?

With an output schema present, the return value burden is reduced. The description covers the core purpose and parameters, but for a tool with 2 parameters and no annotations, it leaves gaps in parameter semantics and behavioral context. Adequate but not thorough.

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 description coverage is 0%, so the description must explain parameters. It mentions domain and days in a template but does not add meaning beyond the field names (e.g., what is the valid range for days? Is domain a full domain or part?). The default for days (30) is not mentioned.

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?

Description clearly uses a specific verb ('get') and resource ('certificates') with an explicit filter (expiring within days). It distinguishes from sibling tools like get_certificate (single cert) and get_domain_certificates (all certs) by focusing on expiry.

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?

Usage is implied (when you need certs expiring soon) but no explicit guidance on when not to use it or which sibling to choose instead. The description lacks exclusion criteria or alternative suggestions.

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