Trigger Lucky certificate sync

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

Annotations tell us it is not read-only, not idempotent, and not marked destructive, but the description adds no behavioral details beyond the triggering action. It does not explain side effects, asynchronous behavior, failure modes, or whether existing certificate data is modified.

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?

A single, front-loaded sentence with no filler. Every word adds meaning, and the key qualifier 'existing' is placed early to prevent misuse with new certificates.

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 one-parameter triggering tool, the description gives enough to invoke it, but it omits expectations around return values, error conditions, and what 'ACME/manual' implies about mode selection. It is adequate but leaves notable operational gaps.

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?

With 0% schema description coverage, the description must compensate, and it does by clarifying that `key` refers to an existing certificate key. It stops short of describing key format, origin, or usage examples, but for a single simple parameter it provides meaningful context.

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 uses a specific verb ('Trigger') and resource ('certificate sync'), with the qualifier 'ACME/manual' and 'existing certificate key'. It clearly distinguishes itself from cert-related siblings like list/get/bind/add by focusing on the sync action.

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 is given about when to use this tool versus alternatives such as lucky_get_cert, lucky_add_custom_cert, or lucky_bind_cert. The description implies the purpose but provides no context for choosing it over related tools.

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