blogger_posts_list

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

No annotations are provided, so the description carries the burden. 'List' clearly indicates a read-only operation, and mentioning pagination and summary mode offers useful behavioral context. It does not go into details like response format or auth requirements, but for a read-only list tool this is adequate.

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?

A single, front-loaded sentence that states the core action and key capabilities. Every word earns its place with no fluff or repetition.

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?

For a tool with 12 parameters, the description is concise but adequate because the schema richly documents every parameter. With no output schema, the description doesn't detail return structure, but 'List posts' strongly implies the response is a collection of posts. Overall, it provides enough context for an agent to select and invoke the tool correctly.

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 100%, so baseline is 3. The description groups parameters conceptually (filtering, pagination, summary mode) but adds no meaning beyond the schema's per-parameter descriptions. It is redundant with the schema rather than supplementary.

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 uses a specific verb ('List') and resource ('posts for a specific blog'), clearly distinguishing it from sibling tools like blogger_posts_get (single post) and blogger_posts_search. It also highlights optional filtering, pagination, and summary mode, which further defines its scope.

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 implies use cases: listing posts for a blog with optional filters and pagination. It gives clear context but does not explicitly mention alternatives or exclusions, such as 'use blogger_posts_get for a single post'. This aligns with 'clear context, no exclusions'.

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