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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses an important refusal condition (already_claimed), platform character limits, and that the edit becomes what gets posted. It does not address errors or persistence details, but the main behavioral risks are covered.

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 description is three sentences, front-loads the core action, and every sentence carries distinct information: what it edits, when to use it, and constraints/refusals. No filler or repetition of the schema.

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 simple three-parameter mutation tool with minimal annotations and no output schema, the description supplies enough context to invoke it correctly, including a key failure condition and length limits. The only minor gap is that campaign_id is not explained, but this is shared campaign context rather than tool-specific behavior.

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?

With two of three parameters described in the schema, the description adds meaning by tying reply_id to get_posts, framing reply_text as a full replacement, and adding X/other character limits. The campaign_id parameter remains undocumented, but the context is mostly recoverable from the campaign workflow.

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 names a specific verb and resource ('Rewrite the text of ONE reply draft') and clarifies scope with 'before the community posts it' and 'exact reply a creator will claim.' This distinguishes it from generation/publishing siblings without needing to open the 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?

'Use it when the user wants different wording on a specific draft from get_posts' states the triggering condition explicitly, and 'Refuses a reply a creator has already claimed ... edit before you publish' provides a clear when-not-to-use constraint. This gives an agent actionable routing guidance.

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