ghost_posts_list

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only states 'Returns posts with metadata.' It omits pagination semantics, default ordering, how the filter/fields/include strings combine, and whether this is a safe read. 'Returns posts with metadata' is too thin for a 7-parameter listing tool with zero annotation coverage.

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?

Two short, front-loaded sentences with no padding; the verb and scope come first. It is efficient, though it is arguably terse rather than rightly sized for a 7-parameter tool.

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?

With no annotations, no output schema, seven parameters, and nine siblings including a near-duplicate search tool, the description should clarify list-vs-search behavior and return shape. As written, key selection and invocation context is missing.

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% and every parameter has an example-bearing description (order, fields, filter, include, formats), so the schema already does the heavy lifting. The description adds only 'optional filters,' which restates rather than extends the schema, making the baseline 3 correct.

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 clear verb+resource ('List posts') and notes optional filtering, which is enough to identify the operation. However, it never distinguishes itself from the sibling ghost_posts_search, which overlaps heavily with listing plus filtering, so the agent must guess which to pick.

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 phrase 'with optional filters' implies a use case but gives no when-to-use, prerequisites, or guidance on choosing between this and ghost_posts_search or the bulk siblings. No exclusions or alternative routing are provided.

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