fetch_posts_by_category

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

With no annotations, description carries full burden. States it fetches data (implied read-only) but does not disclose behavioral traits like auth requirements, rate limits, or side effects. Lacks detail beyond basic operation.

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?

Two sentences plus a structured args/returns block. Purpose is front-loaded. Slight verbosity from docstring format, but no redundant content. Efficient overall.

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 2-parameter tool with no output schema, description covers basics (purpose, params, return type). Lacks details on pagination limits, error handling, or output structure, which would be helpful.

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 0%, so description must compensate. It explains 'category' as the category name and 'page' as page number, adding context beyond schema types. However, it could be more descriptive about defaults or constraints.

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?

Clearly states it fetches posts by category name from WordPress, a specific verb+resource. Distinguishes from siblings like 'fetch_posts' (no category filter) and 'fetch_categories' (different entity).

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?

Implies usage for category-filtered post retrieval but provides no explicit guidance on when to use this tool over alternatives like 'fetch_posts' or 'fetch_post_by_id'. No exclusion criteria or context provided.

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