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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only the loose notion that drafts and publishing states are included; it says nothing about pagination behavior, default limits, or ordering, which would be the valuable additions for a list tool.

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?

A single ten-word sentence with no filler, and the scoping information is front-loaded. It is efficient, though the brevity is achieved partly by omitting information rather than by tight writing.

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 return values need not be described, but an 8-parameter list tool with date filters, a status enum, a platform filter and cursor pagination deserves more than one sentence. Nothing tells the agent about required brandId, default result size, or how to continue a result set.

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 description coverage is 0% across 8 parameters, so the description must carry the burden and largely does not. The mention of 'drafts and publishing states' loosely parallels the status enum, but brandId, since/until, limit, cursor, platform and connectionId are never explained, including the critical fact that responses are cursor-paginated.

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 verb 'Read' plus the objects 'brand calendar, drafts and publishing states' gestures at retrieving scheduled/draft content, but the word 'post' never appears, so an agent must infer that this is the post-listing tool. It is distinguishable from get_post only vaguely, and 'brand calendar' is metaphorical rather than a precise resource name.

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?

No statement of when to use this versus get_post (single item), list_campaigns, or create_draft/update_draft. There is no guidance on paging, time-window usage, or the fact that 'status' can be filtered.

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