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; 'List' reasonably implies a read-only operation, and the status-filter semantics are genuinely added context beyond the structured fields. However, it says nothing about pagination behavior, ordering, or what happens when limit exceeds available posts.

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 compact sentences, front-loaded with the core purpose and then the status filter semantics. Nothing is padding, though the terse format leaves gaps rather than being excessive.

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?

An output schema exists, so return-value documentation is not required. The main remaining gap is the undocumented limit parameter and absence of any pagination or ordering note, which matters for a listing tool defaulting to 20 results.

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. It documents the status parameter's allowed values ('draft | scheduled | posted | failed') and the empty-string default meaning ('empty = all'), which is real added value, but the limit parameter is left completely unexplained.

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 ('posts') with a scope qualifier ('in the local workspace'), so the agent knows exactly what it returns. It doesn't differentiate from the sibling listing tool list_platforms or explain its relationship to generate_posts/check_post, but the action is unambiguous.

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?

No when-to-use guidance, no conditions, no mention of alternatives like check_post for a single post. The purpose is implied by the verb but the agent gets no routing help among the five siblings.

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