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

Annotations declare destructiveHint=true, but the description goes well beyond that: it warns that automatic adaptation can lose intentional formatting, that the mutation is in place on the same post_id, and that synced_platforms creates an ongoing mirror rather than a one-time copy (only valid when source is socials[0]). These are consequences an agent could not infer from the annotation flags alone.

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 core purpose and the update_post alternative are front-loaded, and the prerequisite/validation information is dense and useful. The final two sentences re-explain synced_platforms almost identically to the schema description, which is mild duplication, but nothing else is padding.

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 single nested-request parameter, an output schema, and rich annotations, the description covers everything an agent needs: preconditions, the difference between one-time conversion and ongoing mirroring, the formatting-loss risk, and the natural follow-up call. Nothing material is left unspecified.

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 100% and the nested request object documents post_id, source_platform, target_platforms and synced_platforms thoroughly, including the mirroring rule and the 'must not include the source' constraint. The description largely restates the synced_platforms semantics rather than adding new parameter-level detail, so the baseline of 3 applies.

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 ('Adapt an existing post's content from one platform to one or more others') plus the crucial scoping detail that the update happens in place on the same post_id. It explicitly contrasts itself with update_post for hand-written per-platform content, so an agent can distinguish it from the sibling without opening either schema.

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?

Names the exact trigger ('explicit requests to auto-adapt content, e.g. convert this to LinkedIn'), the alternative route (hand-written content goes through update_post), the follow-up tool (validate_post_content), and the preconditions on source/target platforms. The synced_platforms paragraph further states when mirroring applies versus a one-time conversion.

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