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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, yet the description still adds real behavior: sort order ('newest-scheduled first'), page size ('20 per page'), and the returned field set. It does not mention auth requirements, rate limits, or total-count behavior. No contradiction with 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?

The purpose and sort/pagination facts are front-loaded, and the second sentence handles filtering efficiently. The mid-sentence field enumeration is a run-on but each field earns its place given there is no output schema.

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 correctly compensates by naming the returned fields, pagination size, and sort order. Only pagination termination/total-count behavior is left unstated, which is a minor gap for a default-filtered list tool.

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 3 is the baseline, but the description adds intent-level meaning to the status enum — tying 'pending/queued' to the content calendar and 'published' to what already went out — which the enum alone does not convey. tag_id and page get no extra color beyond 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 ('List the user's scheduled and published posts') and enumerates what each row carries, so an agent can tell it apart from generate_posts or create_post_tag. It stops short of differentiating from close siblings like list_drafts or get_calendar, which also deal with post timing.

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 maps intent to filter values ('queued or pending for what is coming up — the content calendar — or published for what went out'), which is genuine usage guidance for the status parameter. However, it never says when to reach for this tool instead of list_drafts, get_calendar, or list_persona_replies, so the when-to-use dimension is only implied.

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