list_posts

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

No annotations are provided, so the description carries the burden. The verb 'List' implies a read-only operation, but the description does not explicitly state non-mutating behavior, pagination, return format, or other caveats. It adds little beyond the basic purpose.

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, well-structured sentence with no unnecessary words. It is front-loaded and directly states the core action and filtering options.

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 the low complexity (2 optional parameters, no output schema), the description covers the essential usage. It mentions the account scope and filter dimensions. Minor gaps like pagination or return format are not critical for a simple list tool, but without annotations there is room for more detail.

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?

With 0% schema description coverage, the description compensates by saying 'optionally filtered by status or platform,' indicating the parameters are filters. However, it does not explain enum semantics or default behavior; the schema provides the allowed values. This adds some meaning but is not extensive.

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 a specific verb+resource construction: 'List posts on this QPost account, optionally filtered by status or platform.' It clearly distinguishes from siblings like list_connected_accounts (which lists accounts) and get_post (which retrieves a single post).

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 use when you need to list posts, with optional filters. It does not explicitly mention alternatives or when not to use this tool, relying on the name and resource reference to differentiate it from siblings like update_post or get_post.

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