sdcloud_get_delete_certificate_status

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

The description implies a read operation but fails to disclose behavioral traits such as that it polls an async job, expects a job ID from a previous delete call, or has no side effects. No annotations are provided, so the description should carry the full burden, which it does not.

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 very concise (one line) but lacks necessary detail. It is front-loaded but incomplete, making it adequate but not excellent.

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 no output schema and no annotations, the description should provide more context about async polling, expected inputs, and response. It fails to mention that this is a status check for a previously initiated deletion, leaving the agent underinformed.

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 description coverage is 0%, so the description must explain parameters. However, the description provides no explanation of what 'delete_certificate_id' represents (e.g., job ID from a delete call). The parameter name offers a hint, but the description adds no value.

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 gets the status of a certificate-delete job. The verb 'Get' and resource 'status of a certificate-delete job' are specific. However, it does not distinguish from similar status tools for other operations (e.g., install), missing the async job polling 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 versus alternatives like sdcloud_get_install_ca_certificate_status or when to call after initiating a deletion. No mention of prerequisites or alternatives.

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