List posts

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

With no annotations provided, the description carries the full behavioral burden. It discloses pagination behavior (default 20/page, max 100), optional status filtering, and the required API key scope. This goes well beyond a simple 'list posts' statement, providing useful operational details.

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 two sentences, front-loaded with the primary action, and every sentence adds value. It efficiently covers the core function, pagination, filter, and scope without any fluff or redundancy.

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 description is sufficiently complete for a simple list tool with three optional parameters and no output schema. It covers the essential context: what it lists, pagination limits, available filters, and authentication requirement. It does not describe response shape, but this is not critical for a list operation and no output schema exists to contradict it.

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 schema description coverage is 100%, so all parameters are already documented (page, status, perPage). The description mostly restates what the schema says (default 20/page, max 100, status filter) without adding new meaning or clarifications beyond the structured schema.

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 the tool's verb and resource: 'Lists blog posts for the authenticated tenant.' It also specifies pagination and optional status filtering, which distinctly separates it from sibling tools like get_post (single post) and create_post/update_post/delete_post (mutations).

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?

The description provides clear context for when to use the tool: to list posts with pagination and optional status filters, requiring posts:read scope. It does not explicitly mention alternatives or exclusions, but the context is sufficient for an agent to understand its typical use case compared to sibling tools.

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