List Blogposts

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds behavioral specifics: filtering by space/status, sort order examples, pagination via cursor, and limit constraints (default 25, max 250), which go beyond the structured data.

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 a single purpose line followed by a concise args list. Every sentence adds useful information, with no fluff. The main purpose is front-loaded, and the parameter descriptions are compact yet complete.

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?

Given the tool has no output schema, the description covers the parameter space and pagination behavior well. It does not explicitly describe the response structure or that results are returned under a key, which could be useful for a list tool. Still, the description is quite complete for the scope.

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?

With schema description coverage at 0%, the description carries full burden. It explains every parameter meaning: space_id restricts to a space, status filters to 'current' or 'draft', sort provides examples, cursor is from a previous response, and limit specifies default/max. This fully compensates for the schema's lack of enums and details.

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 'List blog posts, optionally filtered by space' — a specific verb and resource. However, it does not differentiate from sibling tools like list_blogposts_in_space or list_blogposts_with_label, so it misses explicit sibling differentiation.

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 explains how to use each argument but gives no guidance on when to choose this tool over list_blogposts_in_space or list_blogposts_with_label. The optional space filter is implied as a unified interface, but no exclusions or alternative conditions are mentioned.

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