ncloud_gtm_update_policy

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

Annotations indicate idempotentHint=true and destructiveHint=false, which are clear. The description adds no further behavioral context (e.g., partial update behavior, required permissions). With annotations covering safety, a score of 3 is appropriate as the description adds minimal value beyond structured hints.

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?

One concise sentence with no fluff. Every word is relevant and essential. Ideal 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?

With 6 parameters including nested objects and no output schema, the description is minimal but functional given complete schema. Lacks guidance on partial updates or effect of optional fields. Annotations cover safety, so overall it is adequately complete for a tool with rich schema but could be improved.

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 100%, so baseline is 3. The description does not add any parameter-level details beyond what is in the schema. It does not compensate for missing information, but schema itself is thorough.

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 clearly states 'Update an existing Global Traffic Manager policy' with a specific verb (Update) and resource (Global Traffic Manager policy). It effectively distinguishes from sibling tools like create, get, delete policy.

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. The description does not provide context for when an update is appropriate, prerequisites, or mention related tools like create or get policy. A score of 2 reflects missing usage context.

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