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

Annotations already flag this as non-read-only, open-world, non-idempotent, and destructive. The description adds valuable context beyond annotations: the reply is public, immediate, tied to the connected account, limited to one lead, and consumes the workspace's monthly X posts. It does not cover failure modes or whether a posted reply can be deleted.

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 critical action and scope are front-loaded in the first sentence. The remaining sentences add permissions, single-lead constraints, parameter guidance, and quota impact without unnecessary 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 public, destructive, open-world mutation, the definition covers authorization, scope, account context, and quota consumption. It stops short of explaining failure behavior or whether the posted reply can be edited or removed, but the safety-critical context is largely present.

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%, so the schema already documents all four parameters, including lead_id and brand_id sources. The description reinforces that text is for user-edited drafts and is capped at 280 characters, but adds little beyond the schema and says nothing about user_goal.

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 states a specific verb and resource: it POSTS a public reply on X under the connected account to ONE lead sourced from list_reply_leads. This clearly distinguishes it from sibling tools such as queue_post_for_publishing, update_social_post, or dismiss_reply_leads.

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?

It gives explicit conditions: only after the user has read the lead and reply and said yes, never for several leads on one go-ahead, and never on the agent's own judgement. The prerequisite source tool and the single-lead scope are also named.

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