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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered structurally. The description still earns credit for spelling out the destructive mechanics (whole-collection replacement, omitted items deleted) and ID retention, which annotations don't convey. It stops short of permissions/auth specifics or the overlap with media_kit_set_sharing, so it's good but not full.

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, front-loaded with the replace scope, then the destructive consequence, then ID retention, then visibility semantics. No redundant restatement of the name or title and no filler.

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?

With an output schema present and full parameter documentation, the description covers the risky semantics an agent most needs before calling a destructive batch replace. The remaining gap is that a sibling tool appears to handle sharing/visibility separately, and the description doesn't disambiguate that overlap.

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 100%, establishing a baseline of 3, and the description genuinely adds meaning on top: replace-not-merge semantics, deletion of omitted items, and preservation of existing IDs. Explaining 'link' and 'private' visibility also goes slightly beyond the schema's own enum description. It does not address the relationship between the visibility parameter here and the media_kit_set_sharing tool.

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 uses a specific verb ('Replace') with an explicit enumeration of the resource collections it touches (rates, brand partners, case studies, portfolio videos, statistics visibility) and scopes it to 'one owned kit'. It is clear what the tool does, though it never names the near-siblings (media_kit_upsert_item, media_kit_set_sharing, media_kit_update) that an agent must choose between.

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?

It gives real selection context: only supplied collections are replaced, omitted collections stay unchanged, and items omitted from a supplied collection are removed. The 'owned kit' prerequisite is stated. What's missing is any explicit exclusion — nothing says when to prefer media_kit_upsert_item or media_kit_set_sharing instead, which matters given the overlap on visibility.

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