list_posts

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

With no annotations provided, the description carries the full burden of disclosing behavior. It adds only 'your' (ownership scope) and 'recent' (recency), but does not explain whether drafts and published posts are both included, how results are ordered, whether this is strictly read-only, or what authentication expectations exist.

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?

A single short sentence with no filler or redundant wording. It front-loads the action and resource, which is ideal for a simple list endpoint.

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 has no output schema, so the description should explain what the response contains, but it does not mention return shape, included post fields, status filtering, or ordering. Given the sibling tools include update_post and delete_post, an agent would benefit from knowing whether list_posts returns drafts, published posts, or both.

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?

The input schema already documents both page and per_page with clear descriptions, giving 100% schema description coverage. The description does not add further parameter-level meaning beyond implying a paginated list, so the baseline of 3 is appropriate.

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 a specific action ('List') and resource ('your recent DayBy posts'), indicating a collection-level operation that is distinguishable from get_post's single-post retrieval. It does not explicitly contrast with siblings, but the plural 'posts' and 'recent' make the core purpose 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?

There is no guidance on when to use this tool instead of alternatives such as get_post, update_post, or draft_post. The phrase 'recent posts' weakly implies a browsing use case, but the description does not state when-not-to-use or mention any sibling tool.

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