blogger_comments_list

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that the tool returns an array of comment objects, omitting critical details such as pagination behavior (pageToken, maxResults), optional filters (status, dates), and differences based on the 'view' parameter. The tool name suggests a read operation, but the description does not reveal these nuances.

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 two short sentences, front-loading the core action and resource. It contains no filler, and every word contributes to the basic understanding of the tool's purpose.

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?

The description is inadequate for a tool with 9 parameters and no annotations. It fails to mention optional filtering capabilities (status, date ranges), pagination, or the impact of the 'view' parameter. The schema details parameters but does not provide usage context, and the description does not fill this gap, making it incomplete for an agent to select and invoke the tool effectively.

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 descriptions for 100% of parameters, so the baseline is 3. The description adds no additional parameter semantics beyond the generic 'all comments', leaving interpretation of filters and pagination to the schema. Since schema already covers everything, a 3 is appropriate.

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 the action ('List') and resource ('comments for a specific post'), which distinguishes it from the sibling 'blogger_comments_listByBlog' through the 'specific post' qualifier. However, it does not explicitly name the sibling or contrasting use cases, so it falls short of full 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 provides no explicit when-to-use or when-not-to-use guidance. The phrase 'for a specific post' implies a use case, but it does not mention alternatives like blogger_comments_listByBlog or define scenarios where this tool should be avoided, such as when needing comments across a blog.

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