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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds nothing behavioral beyond that — no pagination or ordering semantics despite a limit parameter, and no note on how unpublished vs published posts differ — so it is minimum-viable rather than additive.

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 front-loaded sentence with no filler; scope and returned fields come first. It is efficient, though so terse that it omits useful qualifiers rather than being padded.

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?

There is no output schema, and the description partially compensates by naming the returned data (status, schedule time, metrics for published posts), which is genuinely useful for a read tool. Gaps remain around result ordering and pagination, but nothing needed to issue the call is missing.

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 100%: limit (default 25, max 100), status enum with default, and workspace slug are all documented in the schema. The description only gestures at 'status' and adds no syntax or defaulting detail beyond what the schema already carries, so the 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?

Specific verb+resource ('List posts') with a stated scope ('in the workspace') and the fields surfaced. It does not name or contrast any sibling such as get_post_metrics or get_post_insights, so the agent must infer the boundary itself.

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 when-to-use guidance and no exclusions. With 30+ siblings including list_accounts, list_workspaces, get_post_metrics and get_analytics, the description never states that this is the bulk-listing entry point rather than a per-post or analytics tool.

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