ncloud_add_process_plugin

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

Annotations only indicate destructiveHint: false. The description does not disclose whether adding is additive or replaces existing plugins, behavior on duplicates, prerequisites (e.g., server state), or side effects. Lacks necessary behavioral context beyond stating it adds.

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?

Two sentences with no extraneous information. Front-loaded with the action and resource, followed by parameter detail. Efficient and to the point.

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?

Adequate for a simple add tool with three parameters and no output schema. Lacks description of return value or error conditions, but input is well-covered. Missing guidance on usage context (e.g., prerequisites, alternatives) limits completeness.

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 coverage is 100%. Description adds value by specifying that configList accepts process names and supports wildcards like '*abc*', which is not in the schema. This clarifies usage beyond basic types.

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?

Clearly states the tool adds process monitoring plugin(s) to a server instance. Differentiates from siblings like list, get, remove, and set by using 'Add' (not 'Set' or 'Replace'). Mention of wildcards further clarifies scope.

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 (e.g., ncloud_set_process_plugins for replacement, ncloud_list_process_plugins for listing). Does not provide context for choosing this tool over siblings.

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