transfer_artifact_between_orgs

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

No annotations exist, so the description carries the full burden. It does disclose one real behavioral constraint — the Kiln Business plan gate — which is more than the schema provides. However, for a cross-org ownership mutation it says nothing about whether the source org loses the artifact (move vs copy), whether the operation is reversible, what permissions or dual-org membership are required, or what happens on partial failure.

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 operative sentence is correctly front-loaded and the whole thing is short. But the 'shared workspace — teams, member roles, and access grants' sentence is marketing filler that does not help an agent decide or invoke, and the upgrade URL is promotional rather than operational.

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 destructive-feeling, cross-org ownership mutation with no annotations, no output schema, and zero parameter documentation, the description is thin. An agent still cannot tell what `artifact_type` values are legal, whether the artifact is moved or duplicated, or what a successful response confirms.

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% and all four parameters are bare strings. The description's 'from one org's ownership to another' loosely maps to `from_org_id`/`to_org_id`, but `artifact_type` has no enum and no documented values anywhere, and `artifact_id` is unaddressed. The description does not compensate for the coverage 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 artifact from one org's ownership to another'), which is unambiguous about the operation and its endpoints. It does not, however, differentiate itself from the close sibling `backfill_artifact_into_org`, which an agent could easily confuse with 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?

'Requires Kiln Business' is a concrete prerequisite that gates invocation, which is genuinely useful. But there is no statement of when to choose this over the org-related siblings, no note on what conditions must hold (e.g. membership in both orgs), and the intervening sentence about shared workspaces is a sales pitch rather than usage guidance.

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