cert_renew

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

With no annotations, the description carries full burden. It usefully discloses the underlying command, the minDays skip rule, the port-80 precondition, and the restart consequence ('xray loads the new certificate'). However, it omits the safety-critical fact that the default is a dry run requiring a planHash to actually apply, and says nothing about SSH/permission requirements or failure semantics.

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?

Four sentences, front-loaded with the action and mechanism, and the embedded command is genuinely useful rather than padding. Slightly dense but every clause conveys operationally relevant information.

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?

For a nine-parameter mutation tool with no annotations and no output schema, the description covers purpose, precondition, skip logic, and the restart side effect. It leaves the dry-run/apply two-phase workflow to the schema, which documents it fully, so the remaining gap is minor.

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 100%, so the schema already documents all nine parameters. The description adds only a restatement of minDays/force behavior and nothing about target, batch, or planHash beyond what the schema states, so baseline 3 applies.

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?

States a specific verb (renew) and resource (remnanode TLS certificate), plus the exact mechanism (docker certbot via vps-edge-run.sh). No sibling tool competes for this function, so the agent can identify it immediately.

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?

Provides concrete preconditions ('Port 80 must be publicly open') and the condition under which work is skipped ('more than minDays left unless force'). It does not name an alternative or exclusion, but no sibling overlaps, so the guidance is clear context without exclusions.

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