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

Annotations already declare readOnlyHint and closed-world, so the safety profile is covered; the description adds ordering behavior (planned order vs newest first), pagination semantics (limit + nextCursor), and a genuine cost warning that fields:'full' can run past what the agent can read for a month. It also explains domain states (draft_scheduled never sends by itself, missed posts must be rescheduled). It stops short of describing failure modes or rate limits, so not a 5.

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 the date-range guidance are front-loaded and no sentence is filler, but the single dense paragraph stacks nested parentheticals (the reelPostIds aside embeds a delete_post recommendation) that slow parsing. It would read better split into scope, filtering, and pagination blocks.

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 carries the return-value burden and does so: it enumerates the summary fields (id, status, platforms, times, firstLine, slideCount/style, video length, possibleDuplicateOf, reelPostIds) and contrasts them with fields:'full'. Combined with ordering and pagination rules, nothing an agent needs to call this correctly is missing.

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 the baseline is 3, but the description adds meaning beyond the schema: from/to are both inclusive and 'a week across two months is one call', dates are read on the timeZone clock, and fields:'full' is flagged as long output rather than a richer detail level. It leaves month vs from/to tradeoffs mostly to the schema.

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 plus scope ('the project's posts') and enumerates the status universe it covers (drafts, scheduled, published, failed, missed). It explicitly separates itself from get_post ('returns one post whole') and delete_post, so an agent can choose without opening sibling schemas.

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 concrete when-to-use rules: pass from and to 'to see what is planned in a week', otherwise results come newest first, and narrow with status/platform. It also names alternatives (get_post for a whole post, delete_post for Reel source drafts after user agreement) and explains cursor reuse.

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