list_posts

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

With no annotations, the description takes on full burden. It discloses capabilities (sorting, search, pagination limits) but omits details like read-only nature, default behavior, auth requirements, or response format. It provides some transparency but not comprehensive coverage for a tool with no annotations.

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, concise sentence that front-loads the purpose. However, it includes a potentially misleading 'sorting' term not backed by the schema, which slightly reduces clarity. No wasted words, but could be tighter.

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 list tool with two optional parameters and no output schema, the description covers the basics (search, pagination) but leaves gaps: no mention of default limit behavior, sorting mechanism, or what fields the returned posts contain. It is minimally sufficient but not rich.

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 coverage is 100% for both parameters (limit and search), so baseline is 3. The description mentions 'search' and 'pagination limits' but does not add detailed meaning beyond the schema. It also mentions 'sorting' which is not reflected in the schema, creating a minor inconsistency but not detracting significantly.

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 clearly states the action ('Retrieve a list') and the resource ('posts/AI prompts from AR LABS'), and includes scope hints like sorting and pagination. It distinguishes from siblings like 'list_comments' and 'get_post' by focusing on listing all posts, though 'all' is qualified by pagination limits.

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 explicit guidance on when to use this tool vs alternatives. It implies listing use case, but doesn't mention when not to use it (e.g., for a single post use get_post) or any exclusions. The description only states the action without context on selection.

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