ncloud_dataforest_reset_kerberos_keytab

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

No annotations are provided, so the description must carry the behavioral context. It only states 'Reset' without disclosing any side effects, such as whether this invalidates existing credentials or requires authorization. A reset operation implies disruption, but this is not explicitly communicated.

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 concise sentence that states the core action and resource without any extraneous words. It is front-loaded and every word adds value.

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 simplicity of the tool (one parameter, no output schema), the description is insufficient. It does not indicate what happens after a successful reset (e.g., no output format, no confirmation of change). A more complete description would mention, for example, that a new keytab is generated or that multiple services need updating.

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% for the single parameter 'id', which is fully documented in the input schema. The description does not add any additional context beyond what the schema provides, so the 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 explicitly states the verb 'Reset' and resource 'Kerberos keytab for a Data Forest account'. This clearly distinguishes it from the sibling tool 'ncloud_dataforest_get_kerberos_keytab' which retrieves the keytab. The purpose is specific and unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives, such as when a keytab should be reset versus other operations. There is no mention of prerequisites, contextual triggers, or conditions that warrant a reset.

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