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

Annotations declare the safety profile (readOnlyHint false, destructiveHint false, openWorldHint false), and the description adds real behavioral context: the voice engine runs, channel_copy preserves the post's media and schedule and publishes that text on that channel, and the original remains restorable in version history. It doesn't say what the call returns or whether the rewrite overwrites anything visible immediately.

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?

Purpose is front-loaded, followed by example utterances and then the save_as decision rule. Every sentence carries information, though the version-history sentence at the end is the least load-bearing and the examples duplicate phrasing an agent could infer.

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 3-parameter mutation with no output schema, the description covers the main decision (channel_copy vs new_draft) and its side effects well. The notable gap is that it never says what comes back — the rewritten text, an id, or a draft object — which matters when chaining to a publish step.

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%, so baseline would be 3, but the description adds meaning beyond the schema for save_as — that channel_copy keeps media and schedule, publishes on that channel, and stays in version history. The platform parameter is only elaborated via the Instagram constraint already present in the schema.

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+resource ("Rewrite an existing draft") plus a target dimension ("for a specific platform") and adds that the voice engine runs. It does not explicitly distinguish itself from near-siblings like revise_draft, update_draft, or draft_variations, so the agent must infer the boundary.

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?

Gives concrete trigger phrases ("rewrite 123 for Twitter", "make that work on LinkedIn") and an explicit when-to-use rule for save_as: channel_copy ("when the user wants one post on several channels with different text"), plus the default behavior. It stops short of naming alternative tools for adjacent jobs such as revising or updating a draft.

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