get_expiry_report

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

No annotations provided; description only hints at read-only behavior ('stored certificate data'). Lacks disclosure of side effects, rate limits, or authentication requirements. Return format is not described despite having an output schema.

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?

Single sentence with clear subject and qualifier. No extraneous information; efficiently conveys core 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?

Low complexity (zero parameters, output schema exists). Description covers purpose adequately, but lacks guidance on output structure or use cases. However, output schema mitigates need for return format details.

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 tool has zero parameters, so no parameter documentation is needed. Baseline of 4 applies as description adds no value but also doesn't need to.

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 states the tool returns stored certificate data categorized into critical, warning, and ok. Verb 'Return' and resource 'stored certificate data' are specific, distinguishing it from sibling tools like scan_all or check_certificate.

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 on when to use this tool versus alternatives like check_certificate or scan_all. The description implies a read-only report but doesn't specify context or limitations.

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