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

Discloses exactly what the copy lacks — accounts, posts, sequences, team members, HTTP keys — and that it lands turned off, which goes well beyond the annotations (destructiveHint=false, openWorldHint=true). The prompt-injection caution about treating copied texts as the author's content is a genuinely valuable behavioral warning that no structured field conveys.

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?

Three tight sentences: identity of the operation first, then the material state of the imported automation, then the required follow-up workflow and the safety caution. No filler, and the most decision-critical facts are front-loaded.

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 mutating, open-world import with no output schema, the description covers the critical gaps: side effects on related data, the initial inactive state, and the next-step workflow including the `toComplete` field. It does not describe the overall response shape or error behavior for an invalid/expired link, leaving a small gap.

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 already 100%, so the baseline is 3; the description adds the concrete shared-link URL shape ('https://app.ignix.social/app/automations/shared/…') that the schema only alludes to as 'the shared link, or just its code'. `toComplete` is also introduced as a concept the agent must handle, though it is not tied to a named parameter.

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 and resource ('Add a copy of an automation another Ignix account shared … to this workspace') and pins the input to a shared link format, which separates it cleanly from create_automation, duplicate_automation, and create_automation_from_template. An agent can identify the tool from the description alone.

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?

Gives a concrete post-import sequence (walk `toComplete` with the user, then preview_automation, then set_automation_active), which tells the agent what to do immediately after the call. It does not explicitly name when NOT to use it versus duplicate_automation or create_automation_from_template, so it stops short of full alternative routing.

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