blogger_pages_list

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only mentions 'optional summary mode to strip heavy HTML', but does not state that the operation is read-only, how pagination works, or whether fetchBodies is required to get full content by default. This is insufficient for a tool with zero annotation coverage.

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, front-loaded sentence with clear action and resource. It is efficiently concise, although it sacrifices contextual depth that would earn a 5.

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 7 parameters, no output schema, and no annotations, the description provides only minimal context about return values or operational behavior. The schema fills in parameter semantics, but the description does not convey pagination expectations, response structure, or typical use scenarios, leaving the tool minimally viable but incomplete.

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 input schema provides 100% description coverage for all 7 parameters, so the baseline is 3. The description adds marginal value by hinting at summaryOnly through 'summary mode' but does not elaborate on parameter formats or dependencies beyond what the schema already states.

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 a specific verb ('List') and resource ('static pages for a specific blog'), making its purpose unmistakable. It naturally distinguishes itself from sibling tools like blogger_posts_list (posts vs. pages) and blogger_pages_get (single vs. all pages).

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 about when to use this tool versus alternatives such as blogger_pages_get or blogger_posts_list. The description does not mention any exclusions or preferred use cases, leaving the agent to infer appropriateness from the name alone.

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