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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine context beyond that: pagination continuation via page_token (from next_page_token) and the single-workspace fallback for the workspace slug. It says nothing about ordering, page sizes, or empty-result behavior.

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?

Three short lines with the resource statement front-loaded followed by per-parameter notes; nothing is padded. The inline parameter glossary is a slight departure from prose form but is efficient and easy to scan.

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?

With an output schema present, return values need not be described, and annotations cover the read-only nature, so the remaining burden is mostly parameter and paging guidance, which is largely met. The undocumented limit parameter and the absence of any note on result ordering or page size keep it from being fully complete.

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 0%, so the description must carry the parameter burden, and it documents two of three: page_token is explained as continuation from next_page_token, and workspace as a customer slug that is optional with a single workspace. Only limit (default 20) is left undocumented, a minor gap for an otherwise obvious parameter.

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?

States a specific verb implied by the tool and a concrete resource: 'Local Posts des Standorts' with the post types (Update/Angebot/Veranstaltung) and the fields returned (Status, CTA). This clearly separates it from gbp_create_post and gbp_delete_post by name and content, though it never explicitly contrasts with them.

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?

Usage is only implied by the listing nature of the description; there is no explicit 'use this when...' or exclusion of alternatives such as gbp_get_profile or gbp_performance. The one real usage rule given is that workspace is optional when the account has a single workspace, which is useful but narrow.

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