Manage SSL Certificate

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

No annotations provided. Description only states actions without disclosing side effects (e.g., installing custom SSL may replace existing certificate, or enable_auto may overwrite settings). Lacks behavioral context like permissions or destruction impact.

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, 12 words, no redundancy. However, could be split to clarify conditional parameters per action for better readability.

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?

Missing output schema, no description of return values, no behavioral details for each action. For a tool with 5 params and 3 actions, the description is too sparse to fully inform an AI agent.

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 coverage is 0%, description adds action enum values but does not clarify conditional requirements (certificate_content and key_content only needed for install_custom). No explanation of server_id, app_id syntax.

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 clearly states the tool manages SSL certificates with three specific actions (list, enable automatic SSL, install custom). It distinguishes from sibling tools which focus on deployment, backups, logs, etc.

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 explicit guidance on when to use this tool vs alternatives. The actions are listed but prerequisites or ordering (e.g., need to list before installing) are not mentioned.

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