list_posts

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only says 'list posts', which implies a read-only operation but does not disclose pagination behavior, default ordering, how filters behave, or any rate limits. The absence of any safety or side-effect information is a notable gap for a tool with nine parameters.

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 description is a single, concise sentence that is easy to read and front-loads the primary action. However, it is under-specified given the tool's complexity, and the brevity comes at the cost of necessary detail. It is not overly verbose, but the minimalism limits its usefulness.

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?

The tool has 9 optional parameters, no output schema, and no annotations, yet the description provides no information about filters, pagination, return format, or any constraints. This is highly inadequate for a tool with such a rich input schema. The description fails to provide comprehensive context for an AI agent to use it correctly.

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%, so the description must compensate by explaining parameters. It only says 'optional filters' without elaborating on any of the nine parameters (to, from, page, query, state, states, postType, member_id, account_ids). This provides no additional meaning beyond the bare schema, leaving users to guess parameter formats and semantics.

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 clearly states the action ('List posts') and a key feature ('with optional filters'). It is distinguishable from sibling tools like get_post, which retrieves a single post, and update_post, which modifies a post. However, it does not explicitly mention the scope of posts (e.g., across workspaces or accounts), which could be ambiguous.

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 provides no guidance on when to use this tool versus alternatives such as get_post or schedule_post. It vaguely mentions 'optional filters' but does not explain what filters are available or when they would be used. There is no mention of exclusions or preferred use cases.

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