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

The description indicates a read-only 'check' action but does not explicitly state whether any resources are modified or if external services are accessed. No annotations provide additional safety information, so the description bears the full burden.

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, direct sentence without redundant phrases. It immediately states the action and the subject.

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?

The description covers the core purpose but lacks specification of expected deployment plan format (e.g., Terraform state) and any return value or error conditions. Given the single parameter and no output schema, these omissions are notable.

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?

The parameter 'plan' is described as an object, array, or string, which gives a basic type hint but no field-level details. Since this is the only parameter, the coverage is complete, but the description adds limited structural information.

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?

Clearly states that the tool checks a deployment plan for specific risk categories (sandbox, exposure, IAM, cost). This distinguishes it from other check tools that target artifacts or commands.

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?

Does not provide guidance on when to use this tool compared to alternatives like huaweicloud_hook_check_artifacts or huaweicloud_sandbox_deploy_check. No explicit conditions or examples are given.

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