List Blog Posts in Space

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is clear. The description adds minimal behavioral context beyond the parameter list, such as no mention of pagination behavior or return format, but this is acceptable given the annotations cover the key safety aspects.

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 quite short and gets to the point. The Args block is repetitive but each line is minimal and no unnecessary text is included. It loses one point for the awkward formatting of listing parameters, but overall it is efficient.

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 no output schema, the description should explain return values and edge cases, but it does not. It also fails to differentiate this tool from sibling tools like 'list_blogposts'. The tool is simple, but the lack of any behavioral or return details makes it incomplete for effective selection and invocation.

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 description coverage is 0%, so the description must fully compensate. However, the Args section provides only terse labels like 'Space ID', 'Sort field', and 'Blog post status filter' that add little beyond the schema's property names. No examples, allowed values, or format details are given for sort, status, cursor, or limit, leaving significant ambiguity.

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 in a space' with a specific verb and resource, and the space scope distinguishes it from the sibling tool 'list_blogposts' which likely lists across spaces. This is a clear, specific purpose.

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 like 'list_blogposts' or 'list_blogposts_with_label'. There are no exclusions or explicit alternative recommendations, leaving the agent to infer usage solely from the tool name.

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