ncloud_dataforest_stop_app

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

Description only says "Stop" with no detail on shutdown behavior, timeout, or error states. Annotations provide idempotentHint and destructiveHint, but description adds minimal context beyond those.

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?

Single sentence, no redundant information. Efficiently communicates the tool's purpose.

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?

No output schema, but for a simple stop operation with one parameter and clear annotations, description is adequate. However, lacks details on return value or post-stop state.

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?

Single parameter 'id' is well-documented in schema with description and constraints (Base62-encoded UUID). Description does not add extra meaning beyond schema coverage, so baseline 3.

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?

Description uses specific verb "stop" and resource "running Data Forest app", clearly distinguishing from sibling tools like start_app and delete_app.

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 explicit usage guidance or exclusions; only implied that it stops a running app. Does not state when not to use or alternatives.

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