Check Deployment Status

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

No annotations. The description does not disclose any behavioral traits like side effects, authorization needs, rate limits, or what constitutes 'progress' or 'logs'. Minimal transparency beyond the obvious.

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?

Very concise but borderline under-specified. One short sentence with no waste, but could benefit from slight expansion to include key details without becoming 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 tool has three required parameters and no output schema, the description is incomplete. It does not explain return format, error conditions, or how results are presented. Lacks enough information for an AI agent to use it confidently.

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% with no parameter descriptions. Although parameter names ('server_id', 'app_id', 'deployment_id') are self-explanatory, the description does not add any semantic value or explain their role in context of the check operation.

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 'check' and the resource 'progress and logs for a Cloudways deployment'. It distinguishes from siblings like 'deploy-cloudways-app' (creates) and 'get-cloudways-logs' (might be more general, but this is specific to deployments).

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 versus alternative monitoring tools such as 'get-cloudways-logs' or 'get-server-stats'. Lacks context on prerequisites or when it should be preferred.

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