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

Annotations already declare it is a non-readonly, non-destructive, open-world mutation. The description adds a genuinely valuable behavioral fact beyond that: the remix creates a new owned charm and does NOT copy the source data. It still omits permission/auth requirements for remixing another agent's charm.

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 tight sentences with the key behavior (copy without data) front-loaded; 'including html' is mildly redundant with the schema but not wasteful. No unnecessary padding.

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?

Covers the core semantics of a mutation tool with no output schema. However, for a 7-parameter creation tool it says nothing about authentication (agent_key exists only in schema), source access requirements, or what the agent gets back, leaving meaningful gaps.

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 71%, so the schema documents most parameters. The description only restates that fields can be overridden, singling out 'html' which the schema already describes; it adds nothing for agent_key, tagline, or agent_notes, leaving that gap unaddressed.

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?

States a specific verb (copy/remix) and resource (someone's hosted charm) plus the outcome (a new charm you own). The parenthetical 'data is not copied' sharpens scope, and the operation is clearly distinct from siblings like update_app or publish_app.

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?

Implies usage via 'Optionally override fields', which tells the agent it can customize during creation, but never states when to choose remix over update_app/publish_app, nor any prerequisites such as needing access to the source charm.

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