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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantive behavior beyond that: the URL expires after 24 hours, it works without signing in, and the archive reflects whatever is planned at the moment the link is opened (deferred snapshot, not a frozen export). Those are exactly the operational facts an agent needs and cannot get from structured fields.

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 return value in the first sentence and reasonably dense throughout, with no filler. The prose is somewhat run-on across clauses (scope, output layout, audience, delivery instruction, expiry), so an agent must parse one long block rather than scan discrete lines.

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 compensates well by describing the returned artifact (zip, per-post folders, media, caption .txt, filename metadata) and its lifetime. Minor gaps remain: no mention of failure modes (e.g., nothing planned in the range) or the timezone-required behavior beyond the schema hint.

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%, including the timeZone semantics ('sets the day boundaries and the times in file names') and the days default of 7, so the schema already carries the parameter burden. The description only echoes the 1–31 day range and the per-file naming, adding little beyond structured data. Baseline 3 applies.

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 up front: 'Returns a link to a zip of the posts planned in a week (or any 1–31 days)', plus the exact archive layout (one folder per post, media plus caption .txt, planned time/platforms in filenames). It implicitly separates itself from scheduling/publishing siblings ('For posting by hand or through another scheduler'), but never names an alternative tool, so the differentiation is by scenario rather than by sibling.

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 situational context for choosing this tool: use it when the user will post by hand or via another scheduler, when no account is connected, or when on the free trial. It also gives an interaction guideline ('Give the user the url as plain text'). It stops short of explicit exclusions, such as when to prefer publish_post or create_upload_link instead.

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