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

Annotations only declare non-readOnly, non-idempotent, non-destructive. The description adds rich behavioral context: no second draft is ever started, the brand comes back as a caption with copy pending, an in-progress state means the reply says to call again in seconds, and publishing (not drafting) is where a real connection is required. This is substantial disclosure beyond the annotations.

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 content is a single sprawling paragraph riddled with nested parentheticals, so the load-bearing distinction between count=1 and count=3-5 is buried mid-sentence rather than front-loaded. It is information-rich but hard to parse and poorly structured.

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?

Given a two-parameter tool with no output schema and non-trivial two-mode behavior, the description covers the workflow, prerequisites, defaults, and downstream steps thoroughly. It is essentially complete, only slightly under-explained on how the returned draft/caption is shaped.

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% and both params are documented, but the description adds interpretation beyond the schema: it explains what count=1 vs count=3-5 actually returns, and characterizes when a brandId has a usable voice sample (connected account or non-thin website scan). This goes past the schema's field-level wording.

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 (drafts) and resource (posts) and clearly splits the two modes: count=1 returns the brand's single auto-written first post, while count 3-5 drafts a batch from the brand's own voice. It is dense but an agent can distinguish this from create_post/create_adhoc_post.

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 when-to-use guidance for both modes (count 1 default; use 3-5 right after create_brand so there's a real batch) and names the concrete next-step alternatives: approve_copy, approve_post, then publish_post or schedule_post. It also names prerequisites (voice source) and the alternative paths (create_brand's connectSocialFirst, list_connections).

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