list_blogs

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

With no annotations, the description carries the behavioral transparency burden. It discloses that the tool lists portal-level blog instancesparen rather than posts, and that it exposes blog_id values needed by another tool. While it does not explicitly state side effects or filters, the list operation and its output purpose are clearly communicated.

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 sentences with no redundancy. It front-loads the action, provides clarifying examples, and then gives a concrete use case. Every sentence earns its place.

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 zero-parameter list tool with an output schema, the description is complete. It tells the agent what the tool lists, gives examples, and explains how the result will be used. Nothing important is missing for correct invocation.

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 tool has zero parametersharein, so the schema already covers everything. The description adds useful downstream context about blog_id, but there are no parameter semantics to clarify. Baseline 4 for zero-parameter tools 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 a specific verb and resource: 'List the blog instances in the portal.' It reinforces the distinction with concrete examples ('a marketing blog and a tech blog') and explains the intended outcome ('get the blog_id'), making it easy to distinguish from sibling tools like list_blog_posts.

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 clear usage context: 'Use this first to get the blog_id that create_blog_post_draft needs.' This tells the agent when to call the tool. It does not explicitly mention alternatives or when not to use it, but the downstream workflow guidance is strong and relevant.

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