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

Annotations already declare readOnly, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: results are paginated, workspaceId is mandatory, and the null-vs-zero metrics distinction prevents a common misreading. It omits return ordering and total-count behavior, keeping it short of a 5.

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-loads purpose, scope and pagination in the first sentence, then devotes the second paragraph solely to the non-obvious metrics option. Every sentence carries information; the enumeration of statuses is the only mild redundancy.

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?

Nine parameters with a required workspace and no output schema—the description covers pagination, the required param, status vocabulary and the metrics payload well enough to call the tool correctly. It leaves the response envelope (items array, total pages) and default sort order undocumented, which a caller would want before building on the results.

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 baseline is 3, and the description earns above that by explaining includeMetrics semantics and what a null metrics value means, which the schema alone does not convey. Status values are restated from the enum, adding little, and the to/from date-filter semantics are left entirely to 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 posts with filters') plus pagination and the required workspace scope. It distinguishes itself from the sibling get_post only obliquely ('instead of fetching them one at a time') rather than naming it, so an agent can infer the split but must do a little work.

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 an explicit usage scenario for includeMetrics with a rationale ('compare how posts performed instead of fetching them one at a time'), which effectively routes the agent away from repeated get_post calls. It offers no guidance on when to filter by status/platform versus listing broadly, and no exclusions for the other list_* siblings.

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