sdcloud_deploy_site

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

With no annotations, the description should disclose side effects, sync/async behavior, or preconditions. It only says 'Deploy a site by name', omitting critical behavioral traits like whether it overwrites existing configurations or requires the site to already exist.

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 a single sentence, which is concise, but it is too minimal, lacking necessary details. It earns its place but could be expanded without being verbose.

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?

Given the complexity (deploy action, nested body, no output schema), the description is incomplete. It should mention the deployment process, expected input format, or return value.

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 50% (body has description, site_name lacks one). The description adds no extra parameter information; it does not clarify site_name format or the body structure beyond the schema.

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 verb 'Deploy' and resource 'site' with identifier 'by name'. However, it does not differentiate from sibling tools like sdcloud_create_site or other deploy actions (sdcloud_deploy_firewall_policy), leaving ambiguity about the deployment context.

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 on when to use this tool vs. alternatives (e.g., sdcloud_create_site vs. sdcloud_deploy_site). No context on prerequisites or exclusions.

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