copy_community_plugin_to_local

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

With no annotations provided, the description carries the burden of behavioral disclosure. It clearly identifies this as a copy operation and adds a meaningful behavioral consequence: the local copy is safe from plugin-update overwrites. It does not cover edge cases like existing local copies, but the core behavior and purpose are transparent.

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, well-structured sentence that front-loads the action and purpose, then includes the endpoint. There is no filler or redundant restating of the tool name.

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?

For a simple two-parameter copy tool, the description plus complete schema provides enough information for an agent to decide when and how to invoke it. Return-value details are absent, but the copy action and its purpose are sufficiently described without needing an output schema.

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 fully documents both parameters, including plugin_id's source and force_overwrite's default behavior. The description itself adds no parameter-specific detail, so the baseline of 3 applies because the schema covers parameter semantics completely.

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 uses a specific verb ('Copy') and names the source and destination ('Community plugin' into 'Local plugins'), so the action is unambiguous. It also distinguishes this tool from sibling plugin operations like read_plugin, save_plugin, create_plugin, and delete_plugin by stating its copy-based purpose and the reason for doing it.

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 gives a clear use case: copy a Community plugin locally so edits are not overwritten by plugin updates. It does not explicitly list alternatives or when not to use it, but the stated rationale effectively routes an agent to this tool instead of editing or saving a plugin directly.

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