blogger_posts_get

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

With no annotations, the description carries the full burden. It discloses the read-only nature ('Retrieve') and indicates the return contents (content, metadata, labels, optional comments/images). However, it does not mention authentication requirements, error conditions, or the effect of the 'view' parameter, leaving some behavioral aspects unexplained.

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 no redundant content. It states the action and resource immediately, then follows with a concise list of included data. Every word 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?

Despite having no output schema, the description adequately conveys the return composition and identifies the unique ID as the selection key, enabling differentiation from siblings. It does not elaborate on the view access level or response structure, but for a simple get-by-ID operation, it is sufficiently complete for an agent to select and invoke 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 coverage is 100%, establishing a baseline of 3. The description adds value by grouping parameters conceptually: 'content, metadata, labels' map to default behaviors, while 'optionally comments and images' directly explains the purpose of fetchComments (via maxComments) and fetchImages. This synthesis helps the agent understand the optional flags beyond their schema descriptions.

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 tool retrieves a single blog post by unique ID, using the specific verb 'Retrieve' and resource 'blog post'. It also enumerates included data (content, metadata, labels, optionally comments/images), which distinguishes it from sibling tools like search or list that operate on multiple posts or by path.

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 when the unique post ID is known, but it does not explicitly state when to use this tool versus alternatives like getByPath (which uses path) or list (which discovers posts). No exclusions or alternative suggestions are provided, giving clear context but no direct guidance.

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