list_blogs

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

No annotations are provided, so the description carries the full burden. It discloses that OAuth is required for authentication, which is a key behavioral trait. However, it lacks details on other aspects like whether it's read-only (implied by 'List'), rate limits, pagination behavior, or error handling, making it somewhat incomplete for a tool with no annotation support.

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, efficient sentence that front-loads the core purpose ('List all blogs') and includes essential context ('for the authenticated user' and 'OAuth required') without any wasted words. It's appropriately sized for a simple tool with no parameters.

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 the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It covers authentication needs but lacks details on output format (e.g., what data is returned, structure), error cases, or behavioral nuances like pagination. For a list operation, this leaves gaps that could hinder an AI agent's ability to use it effectively without additional context.

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 has 0 parameters with 100% coverage, meaning no parameters are defined. The description adds context by specifying the scope ('for the authenticated user') and authentication requirement ('OAuth required'), which provides semantic meaning beyond the empty schema. Since there are no parameters, the baseline is 4, as the description compensates adequately for the lack of parameter documentation.

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 all blogs') and the resource ('blogs'), specifying it's for the authenticated user. However, it doesn't distinguish this tool from sibling tools like 'get_blog_info' or 'list_posts', which might also retrieve blog-related information but with different scopes or filters.

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 usage context by mentioning 'for the authenticated user' and 'OAuth required', which suggests when authentication is needed. However, it doesn't explicitly state when to use this tool versus alternatives like 'get_blog_info' (which might fetch details for a specific blog) or 'list_posts' (which lists posts within blogs), leaving some ambiguity in sibling differentiation.

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