fetch_posts

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

No annotations provided. Description discloses pagination details (20 per page, cursor) but does not mention read-only nature, error conditions, or auth requirements. Adequate for a simple fetch tool.

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?

Concise and well-structured: purpose first, then pagination explanation, then parameter descriptions. No unnecessary words.

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?

Covers core functionality (pagination, parameters) but omits details like sorting or filtering. Output schema exists but is not described. Good enough for a straightforward list operation.

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 has 0% coverage, but description adds meaning: campaign_id is 'numeric' (despite string type in schema) and cursor is 'Pagination cursor for next page'. Provides useful context beyond schema types.

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 'Fetch posts from a campaign with pagination.' Distinguishes from siblings like fetch_post (singular) and fetch_campaigns (different resource).

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?

Describes pagination usage but lacks explicit when-not scenarios or alternatives. Sibling names imply differentiation, but not directly stated.

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