blogger_blogs_get

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

With no annotations provided, the description carries the transparency burden. It correctly labels the operation as 'Retrieve' (read-only) and lists return fields, but it omits details like permission requirements, error behavior, and the effect of view/maxPosts parameters.

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?

Two short sentences deliver the purpose, method, and return content without redundancy. The structure is front-loaded with the action and qualifies the scope immediately.

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 simple read operation, the description plus complete schema coverage is mostly sufficient. It provides representative return fields, though the lack of an output schema and annotations means some behavioral aspects are left unspecified.

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 description coverage is 100%, so the parameters are already well-documented. The description adds minimal semantic value beyond reaffirming that blogId is the lookup key; it doesn't elaborate on view or maxPosts.

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 it retrieves a single blog's metadata using a unique blog ID. This specific verb-resource relationship and the ID-based lookup distinguish it from sibling tools like getByUrl and listByUser.

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 gives clear context: use this tool when you have a blog ID and need metadata. However, it doesn't explicitly mention alternatives or when-not-to-use cases, so it stops short of a perfect score.

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