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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral context: the two-minute lead-time requirement, the auto-publishing consequence of every occurrence, and the caution to verify content/schedule before calling. It does not cover auth requirements, rate limits, or failure behavior, but it goes meaningfully 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?

Three sentences, no filler, and the most consequential constraints (timing rule, weekday encoding, irreversible auto-publish) are front-loaded. Each sentence adds a distinct fact an agent needs before calling.

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 12-parameter tool with a deeply nested platformOptions object, 50% schema coverage, and no output schema, the description covers the scheduling essentials but omits how the three end-condition parameters relate and what platformOptions actually gates per network. Adequate but with clear gaps given the tool's complexity.

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 50%, so the description has to compensate but only partially does. It usefully pins down two undocumented semantics: weekdays run 0 (Sunday) to 6 (Saturday) and startsAt must be at least two minutes out. It leaves interval, timezone behavior, media, and the endType/endDate/occurrenceCount relationship unexplained, despite mentioning the 'end condition' as a thing to confirm.

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 ('Create a recurring social media post'), and 'recurring' distinguishes it from the one-time publish_post sibling. However, it never explicitly contrasts itself with update_recurring_post or publish_post, so the agent must infer the boundary from the name alone.

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 a precondition ('first occurrence must be at least two minutes in the future') and a pre-call checklist ('confirm the content, account, schedule, and end condition'), which is useful. But it never says when to choose this over publish_post (one-time) or update_recurring_post (edits to an existing schedule), so usage is only implied.

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