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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuine value beyond them: no persistence, existing-ID validation, recorded source revision guards, and rejection of arbitrary media URLs/paths. It stops short of describing what the validation result actually reports or whether validation is all-or-nothing across the bundle.

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 purpose is front-loaded in sentence one and every sentence conveys real information, but the body is a dense seven-sentence prose block describing a deeply nested schema where bullets or field grouping would aid scanning. No sentence is pure filler, but readability of the structural rules suffers.

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?

An output schema exists so return values need not be explained, which helps. However, for a tool with three top-level parameters wrapping dozens of nested fields, the description covers only the posts/mediaRequest half of the contract and omits the ideas payload and all three update arrays, so an agent would still need to reverse-engineer much of the schema.

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?

At 0% schema description coverage, the description carries the full burden, and it only partially delivers: it explains Post structure (key, sharedText, variants belonging to the same Post), that mediaRequest is distinct from post text, inputSources fields and the role enum, and the opaque channel_ selector format. It says nothing about the idea fields, the ideaContentUpdates/ideaSourceUpdates/ideaTaxonomyUpdates arrays, postLinks, attachedIdeaId, or idempotencyKey, leaving much of a very large nested schema unexplained.

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 ('Validates a complete bundle of new Ideas, post drafts, and supported links') and adds a critical scope qualifier, 'without saving the content objects,' which separates it from any commit/write sibling. The bundle-level scope implicitly distinguishes it from the narrower preview_* siblings, but it never names them.

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 description makes clear this is a whole-bundle dry-run, so usage is inferable, but it never states when to choose it over preview_idea_edit, preview_content_variant_edit, or preview_post_media_request_change for single-object checks. No prerequisites or exclusions are given.

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