fetch_posts

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

No annotations are present, so the description must fully disclose behavioral traits. It only mentions the return type ('dict') but omits details on authentication, rate limits, error conditions, or the nature of the API endpoint. The description adds minimal behavioral context.

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 concise and structured with a clear purpose statement followed by Args and Returns sections. Every sentence adds value without redundancy. It is front-loaded and easily parsable.

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 paginated fetch, the description covers the basic functionality but lacks completeness in areas like error handling, response structure details (beyond 'dict'), and usage context relative to sibling tools. The absence of an output schema is partially mitigated by mentioning the return type.

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 description repeats the parameter names and types from the schema, adding brief semantics: 'the page number' and 'the number of posts per page'. However, with 0% schema description coverage, the description only partially compensates by offering basic meaning, not deeper context like valid ranges or pagination behavior.

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 'Fetch posts from a WordPress site' with a specific verb and resource. It distinguishes from siblings like fetch_categories and fetch_pages, though could further clarify differentiation from fetch_post_by_id and fetch_posts_by_category.

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 provided on when to use this tool versus alternatives such as fetch_post_by_id for individual posts or fetch_posts_by_category for filtered results. The agent is left to infer usage from the tool name alone.

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