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

Annotations only declare the mutation profile (readOnly=false, destructive=false, idempotent=false); the description adds substantive behavior beyond that: output is drafts, a voice source must be real, a confident website scan defaults the target platform to Facebook until a channel is connected, and publishing is where a connection is actually required. No contradiction with annotations, and the state-transition chain (draft → approve → publish/schedule) is disclosed.

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 and key constraint are front-loaded, but the description is a single dense sentence with three stacked parentheticals and repeats the count guidance already present in the schema. It earns most of its length but could shed the duplicated count advice and one nested aside without losing information.

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?

With no output schema, the description correctly explains what comes back (drafts under 'your own posts') and what to do next, plus the prerequisites and the default-platform fallback. It is nearly complete for this tool's complexity; only failure modes (e.g., thin website scan blocking a draft) are implied rather than stated.

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 both parameters are already fully documented in the schema, including the 1-5 range and the brandId voice-source requirement. The description restates the '3-5 for a real first-run batch' guidance rather than adding new syntax or constraints. Baseline 3 is appropriate when the schema carries the parameter semantics.

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 ('AI-drafts 1-5 posts') with explicit scope (1-5, from the brand's own voice) and clearly separates itself from create_post/create_adhoc_post by noting output lands as drafts, not published posts. It also names the downstream siblings (approve_post, publish_post, schedule_post), so an agent can place the tool in the workflow without opening any 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?

Gives explicit when-to-use conditions ('no brand guide or strategy required', 'no connected channel required') and states the alternative path when a real connection is needed (publish_post / schedule_post, see create_brand's connectSocialFirst path or list_connections). It also names the required precondition (a real voice source: connected account bio/recent posts or a non-thin website scan), which is exactly the routing information an agent needs.

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