sysknife_get_certificates

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so repeating 'read-only' adds little. The one genuinely additive item is the prerequisite 'needs certbot installed', but the description says nothing about what happens when certbot is absent, what fields certificates carry, or how expired certs are reported.

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?

Front-loaded and short, with the resource named in the first clause. Minor waste from saying 'read-only' twice, once in the action prefix and again as a trailing clause that the annotations already cover.

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 parameterless, non-destructive read with full annotation coverage and no output schema, the description supplies everything needed to decide to call it: what it lists and the certbot dependency. Only the failure behavior / return shape is left implicit, which is a small residual gap.

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?

Zero parameters, so baseline is 4. The description confirms 'no params', which matches the permissive object schema and removes any doubt about whether arguments are expected.

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 gives a concrete verb (list) and resource (certbot-managed certificates), plus the namespaced action `GetCertificates`, so an agent can tell exactly what it returns. It is distinguishable from the many sysknife status/list siblings by its certbot-specific scope, though it never names a sibling to route away from.

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?

It states the operational context clearly: no parameters are needed and certbot must be installed, which is the key precondition for a meaningful call. There are no exclusions or explicit alternatives, but the resource is unique enough among siblings that none is strictly required.

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