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

Annotations already cover read-only/non-destructive, and the description adds real behavioral context beyond them: the PostGroup join, the inclusion of content preview and channelName, the cap at `limit`, and scheduledAt-ascending ordering. Missing only a word on what happens when more than `limit` posts exist (no cursor/offset).

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 tight sentences: resource definition first, then return composition, then limit/ordering. Every clause carries information the caller needs and none is filler.

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?

An output schema exists, so the return shape needn't be explained, and the join/ordering notes are a bonus. The unaddressed `from` parameter is the remaining gap, which for a time-filtered list tool is a substantive one.

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 schema description coverage at 0%, the description must carry the parameter burden. It covers `limit` (cap, implied truncation) and the ordering, but `from` is never mentioned — an agent cannot tell whether it filters on scheduledAt or createdAt and whether it is inclusive.

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 and disambiguates the resource in-line: scheduled means 'queued for publish, not yet sent', which separates it from list_drafts and search_posts. An agent can tell what set of posts it will get without opening the 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?

The scheduled-vs-sent distinction implicitly routes the agent away from this tool when it wants published posts, and the note about filtering by handle client-side usefully signals there is no server-side handle filter. However, no sibling or alternative is named explicitly, so the when-to-use guidance stays implied rather than stated.

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