list_posts

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

With no annotations, the description carries the full burden. It simply says 'List posts' but does not disclose behaviors such as read-only nature, pagination, ordering, authentication requirements, or what the return value contains. This is a significant gap for an annotation-free tool.

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 sentence: 'List posts. kind: 'scheduled', 'published', or 'all'.' It is extremely concise, front-loaded, and every word adds value. No unnecessary fluff.

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?

The tool is relatively simple (one optional parameter, no output schema), so the description covers the basics. However, it fails to mention what the output looks like (e.g., list of post IDs or full objects) and does not hint at whether all statuses other than scheduled/published are included. For a list tool, this is a moderate gap.

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 directly explains the only parameter 'kind' with its allowed values 'scheduled', 'published', or 'all', providing meaning that the schema lacks (no enum). However, it doesn't elaborate on the semantics of each kind.

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 'List posts' with a specific verb and resource, and the kind parameter adds scope. It is clear but does not explicitly distinguish from siblings like content_calendar or post_brief, so it falls short of a 5.

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 usage by listing the 'kind' values but provides no explicit guidance on when to use this tool versus siblings like content_calendar or post_brief. No exclusions or alternatives are mentioned.

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