List posts

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

With no annotations, the description must carry behavioral disclosure. It only states the operation is a list with optional filters/pagination; it does not disclose ordering, defaults, post scope, authentication needs, or what happens when filters are combined. This is minimal behavioral context for a tool with no annotation safety cues.

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 tight, front-loaded sentence with no filler. It conveys the core operation and key modifiers without redundancy, though it is concise because of under-specification rather than completeness.

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 and no output schema, the definition leaves out response shape, default pagination, and any list-scope details. For a tool used for retrieval, these are material gaps, so the description is not complete enough on its own.

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 documentation covers only q (25%), and the description does not compensate for the undocumented limit, offset, and status parameters. Calling these 'optional filters and pagination' gives a rough categorization, but not semantics such as how limit/offset behave or the meaning of the status values.

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 gives a clear verb-resource pair ('List posts') and mentions optional filters and pagination, which distinguishes it from singular/post-focused tools like get_post or create_post. However, it does not explicitly differentiate it from sibling list operations or specify the list's scope, so it stops 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?

No guidance is given about when to use list_posts versus a more targeted tool (e.g., get_post for a single post) or a filtered listing. The phrase 'optional filters' implies filtering, but there are no contexts, exclusions, or alternative tool mentions, so an agent must infer usage.

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