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

The description says 'copy', which implies a non-destructive read-and-create operation, but annotations declare destructiveHint=true. This is a direct contradiction. The description also fails to explain what is copied (e.g., settings, numbers, metadata) or any side effects.

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 sentence, front-loaded with the action and resource, with zero waste. It communicates the essential purpose immediately.

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 clone operation, an agent needs to know what gets duplicated (all settings? numbers? relationships?), whether the operation is synchronous, and potential side effects. The description provides none of this, and the annotation contradiction further undermines confidence.

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 50% (id has 'Pool id' description; name has none). The description adds meaning for the name parameter ('under a new name'), but the id parameter remains ambiguous—it could be the source pool id, but the description doesn't clarify. Marginal benefit over schema.

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 states a specific verb (copy) and resource (sender pool) plus the key mechanism (under a new name). It clearly distinguishes from siblings like create_number_pool, update_number_pool, and delete_number_pool.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The description only implies usage by the word 'copy' but offers no explicit criteria.

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