ncloud_dataforest_set_lifetime

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

The annotations already declare idempotentHint=true and destructiveHint=false. The description adds no additional behavioral context beyond what is already structured. It does not mention consequences of changing lifetime (e.g., whether it takes effect immediately, if the app restarts, or any required states).

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, consisting of a single sentence that efficiently conveys the core functionality. However, it could be slightly expanded to include critical usage context without losing conciseness.

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 no output schema and involves mutation, the description lacks important context such as side effects, required prior states (e.g., app must be stopped?), or whether the change is immediate. Annotations provide some safety info but not enough for complete understanding.

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 input schema has 100% coverage with descriptions for both parameters (id and lifetime). The description does not add extra meaning beyond the schema, but the schema is complete. Thus, a baseline score of 3 is appropriate.

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 ('Change lifetime') and the resource ('Data Forest app'). It uses a specific verb and resource, distinguishing it from other dataforest tools like ncloud_dataforest_set_container_count or ncloud_dataforest_set_quota. However, it could be more precise by explicitly mentioning 'running duration' in a more formal term.

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 usage guidelines are provided. The description lacks any indication of when to use this tool versus alternatives (e.g., when to change lifetime vs. start/stop the app). There is no guidance on prerequisites or context requirements.

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