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

Goes well beyond the annotations: it discloses that no automated posting occurs, the scheduling algorithm (first day with room, 5/day cap, 7-day spacing per account), the override behavior of the date param, and that the queue actively rejects generic praise. These are non-obvious behavioral traits an agent could not infer from readOnlyHint/idempotentHint alone.

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?

Front-loaded with the essential constraint (one post, nothing auto-posted) before the scheduling and voice rules. It is dense and somewhat long, but most sentences carry operational weight; the extended voice guidance is the only portion that could be tightened.

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 9-parameter, no-output-schema mutation tool, the description covers the workflow, scheduling rules, and comment-quality requirements well. Minor omissions remain around the `source` parameter and what the queue returns on success or refusal.

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 only 33% schema coverage, the description compensates by explaining post_url formats (reel//p/), what handle/comment/caption/plays/likes/post date are for, and the YYYY-MM-DD Eastern semantics of `date`. It does not explain the `source` enum's three values, which is the remaining gap.

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+resource ('add ONE specific Instagram post and a drafted comment to the comment queue') and immediately disambiguates from posting tools with 'nothing is posted to Instagram from here.' An agent can distinguish it from siblings like update_ig_comment, ig_comment_queue, and shearquery_instagram_reply_comment 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 clear when-to-use context (drafted comments awaiting a human to post by hand) and the conditions that select the target date. It does not explicitly name the sibling tools an agent might confuse it with, but the human-in-the-loop framing effectively routes usage.

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