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

With no annotations, the description carries the behavioral burden; the verb 'List' implies read-only behavior, and it usefully discloses ordering ('newest first') and the included statuses. It does not explicitly state permissions, default-workspace behavior, pagination semantics, or confirm that no side effects occur.

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 definition is a single front-loaded sentence with no wasted words. It efficiently covers the resource, queue scope, status set, and ordering.

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?

For a simple read-only listing tool with fully documented optional parameters, the description gives enough context about what is listed and how it is ordered. The lack of output schema is partly mitigated by naming the post statuses, though return fields and default-workspace behavior are left to the schema or inference.

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%, so the schema already documents limit, status, and workspace meaningfully. The description mentions the status categories but adds no parameter-specific details beyond that baseline, so a 3 is appropriate.

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 states a specific verb and resource: it lists posts in the queue and names the included statuses. It is clear enough to distinguish a queue listing from mutation tools like create_post or cancel_post, though it does not explicitly contrast itself with get_post_results.

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?

Usage is strongly implied by 'List the queue' with the four statuses, so an agent can infer this is the broad post-listing tool. However, it gives no explicit when-to-use, when-not-to-use, or alternative guidance against siblings such as get_post_results.

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