list_posts

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

With no annotations, the description carries the transparency burden. It adds return fields and filter options but does not explicitly state that the operation is read-only, nor does it describe default pagination behavior or edge cases. The 'list' wording implicitly indicates non-mutation.

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 concise, front-loaded sentences: purpose, filtering, and return data. No unnecessary words or repetition.

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?

Given no output schema, the description covers essential behavior (what it lists, filters, and returns). However, it lacks explicit guidance on when to use this tool vs. siblings and does not mention any limitations or ordering. It is adequate for a straightforward list operation.

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 50% (status and workspace_id have descriptions). The description adds meanings by expanding status values and mentioning pagination, but it does not name limit/offset parameters or specify their roles beyond 'pagination'. Workspace_id is implied by 'in a workspace'.

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 description uses the specific verb 'List' with a clear resource ('posts in a workspace'), and enumerates filters and return fields. It distinguishes the tool from siblings like 'get_post' (single post) and 'list_post_deliveries' (deliveries).

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 description implies usage contexts (listing with status/pagination) but does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions. No reference to sibling tools is provided.

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