timps_certificate_rotator

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

With no annotations, the description must carry the behavioral transparency burden. It clearly says the tool checks, warns, and generates certbot renewal commands, which signals a read/analysis behavior. But it does not explicitly say whether the generated commands are executed, whether files are modified, or how it selects the config files, so transparency is partial.

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 and front-loaded: two sentences that cover the core purpose, the alert threshold, and the expected output. There is no filler or redundancy.

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?

The description provides a reasonable high-level understanding of behavior and output, but lacks enough detail for confident parameterization. Since there is no output schema and no annotations, important context about parameter use and the exact nature of the generated commands is missing. It is usable for basic discovery but incomplete for full operational clarity.

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%, and the description does not explain the `hosts` or `repo_path` parameters. It refers to 'hosts found in config files,' but does not specify whether `hosts` is a filter, what `repo_path` defaults to, or how the parameters interact. The parameter names are guessable, but the description provides very little semantic value beyond 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?

Description uses a specific verb and resource: 'Check TLS certificate expiry for all hosts found in config files.' It also defines concrete behavior: warning at 30 days and generating certbot renewal commands. This clearly distinguishes it from the sibling tools, none of which focus on TLS certificate checking or renewal.

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 intended usage is implied: use this when you need to audit TLS certificate expiry or prepare certificate renewals based on config-file-defined hosts. However, there is no explicit when-to-use vs. when-not-to-use guidance, no prerequisites, and no comparison to alternative tools.

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