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

With no annotations, the description carries the full burden. It does add real behavioral context: the default scope spans all four statuses and results are ordered newest first, which an agent cannot derive from the schema. It says nothing about read-only safety, result shape, or pagination behavior beyond the limit field, so gaps remain.

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?

One sentence, front-loaded with the verb and resource, and every clause (status enumeration, sort order) conveys information the agent needs. No filler.

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 two-parameter list tool with full schema coverage and no output schema, the description covers scope and ordering adequately. It could say more about what each returned post contains, but the core call is unambiguous.

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% with an enum on status and a documented limit range/default, so the schema already does the heavy lifting. The description adds only the ordering guarantee ('newest first') and the fact that omitting status returns all statuses, which is marginal param-level value.

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 ('List') and resource ('the queue') and enumerates exactly what is returned (drafts, scheduled, posted, failed posts) with sort order. It is clear enough to distinguish from siblings like create_post or get_post_results, though it never explicitly contrasts itself with any of them.

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 only implied by the verb and the enumerated statuses; there is no statement of when to prefer this over get_post_results or how it relates to the queue-modifying siblings. No prerequisites or exclusions are given, so the agent must infer the context.

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