List Blogposts With Label

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context about pagination (cursor, limit, default/max) and body_format options, but does not disclose behavior beyond these basics, such as return structure or default ordering. This is adequate but not rich.

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 clear sentence followed by a compact Args list. Every line adds value: no fluff, information is front-loaded, and parameter explanations are concise and 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?

With 6 parameters, no output schema, and no enums, the description covers all parameters meaningfully. It does not explicitly describe the return value, but the 'list' semantics and pagination parameters imply a paginated list of blog posts. Slightly more detail on the response shape would make it fully complete.

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%, and the description fully compensates by explaining each parameter with concrete details: label_id, space_id, body_format allowed values, sort examples, cursor pagination, and limit default/max. This adds strong meaning beyond the bare 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 states 'List blog posts that carry a specific label' with a specific verb and resource, clearly distinguishing it from list_blogposts (all posts) and list_pages_with_label (pages instead of posts). It unambiguously conveys the tool's function.

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 clearly implies usage for filtering blog posts by label, but it does not explicitly compare with alternative tools or provide 'when-not-to-use' guidance. The context is clear, but there are no explicit exclusions or alternatives named.

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