backfill_artifact_into_org

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

With no annotations present, the description carries the full burden, and it does disclose one genuinely useful behavior: the operation writes BOTH the cloud rows and the local ownership marker, which signals a dual-write mutation. However it says nothing about reversibility, permissions, conflict handling, or what happens if the artifact is already in the target org.

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 substantive content is a single well-formed leading sentence. Everything after it is marketing boilerplate ('Business adds team review, approval gates, and 3 printers', a pricing URL) that does not help an agent decide or invoke the tool and dilutes the actual instruction.

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 mutation tool with no annotations, no output schema, and zero parameter documentation, the description should cover permissions, conflict/failure behavior, and valid artifact types. It covers only the high-level effect, leaving an agent unable to predict the outcome of a failed or repeated move.

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 description coverage is 0% for all three parameters. The description names org_id and implies an existing artifact via artifact_id/artifact_type, but never states what artifact_type values are accepted (there is no enum) or what identifier format artifact_id expects, so it only partially compensates for the schema gap.

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 first sentence gives a specific verb and resource ('Move an existing tenant-owned artifact into *org_id*') and even states the dual effect on cloud rows and the local ownership marker. It is clear what the tool does, but it never distinguishes itself from the sibling 'transfer_artifact_between_orgs', so an agent cannot tell the two apart from the text 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?

The only usage condition offered is the licensing prerequisite ('Requires Kiln Business'). There is no guidance on when to use this instead of transfer_artifact_between_orgs, no prerequisites about ownership or tenant state, and no statement of when-not to call it.

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