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

Annotations already declare non-read-only, idempotent and non-destructive, and the description adds real value beyond them: editing re-runs platform checks (length, hashtags, hype words, required settings) and these come back as warnings. It does not say whether warnings block the save or how partial updates behave, but the disclosure of re-validation is substantive.

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?

Two short sentences with zero waste: the mutation scope is front-loaded, followed immediately by the consequence of calling it. No restating of the title or 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?

There is no output schema, and the description helpfully indicates warnings are returned. But it leaves open whether the edit is a full replace or merge of unspecified fields, and gives no handle on the required post_id, which matters for a four-parameter mutation.

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%, so the description must carry the burden, and it names three of the four fields in prose. However it adds no meaning beyond the names — nothing about what the thread array elements represent (separate posts?), and post_id, the sole required parameter, is never mentioned.

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 (Change) and resource (a draft's text, thread or title), and the field list matches the schema exactly. The 'draft' qualifier implicitly separates it from amplify_create_campaign and amplify_schedule_posts, though no sibling is named explicitly.

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 'draft' scoping implies this applies only before publishing, which is useful implied guidance, but it never states when to use this versus amplify_create_campaign or amplify_preview, nor any prerequisites such as needing an existing post_id from amplify_list_posts.

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