yougpu_start_instance

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

Annotations are absent, and the description only says 'Start a previously stopped instance' without disclosing side effects, errors, idempotency, or what happens if the instance is already running. It fails to inform the agent about the tool's behavioral consequences beyond the basic action.

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, focused sentence with no redundant information. It is front-loaded and efficiently communicates the core action.

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?

With no output schema and no annotations, the description lacks crucial context about return values, asynchronous behavior, or failure modes. The sibling tool yougpu_wait_ready implies starting may be asynchronous, but the description does not mention this, making it insufficient for an agent to fully rely on.

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%, and the description does not explain the instance_id parameter beyond what the schema already shows. No semantic meaning is added to aid the agent in understanding how to use the parameter.

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 action with a specific verb 'Start' and resource 'previously stopped instance', distinguishing it from sibling tools like stop, create, and delete. It unambiguously conveys what the tool does.

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 is provided on when to use this tool, prerequisites (e.g., the instance must be stopped), or alternatives. The existence of sibling tools like yougpu_wait_ready suggests a follow-up action, but the description gives no context.

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