gmb_v4_accounts_locations_localposts_list

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safe read operation is known. The description adds no extra behavioral context beyond the API path, aligning with the annotations and providing minimal additional value.

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?

A single, front-loaded sentence effectively conveys the operation, with no wasted words or redundant information.

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?

The tool is a simple list operation with 3 parameters and no output schema. The description covers the core action and scope, but it does not mention pagination behavior or what the response would contain, and it leaves pageSize/pageToken semantics unexplained.

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 compensate. The parent parameter is somewhat explained by the path template 'accounts/*/locations/*', but pageSize and pageToken are not described at all, leaving their roles ambiguous.

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 explicitly states 'Lists local posts for a location' with a specific verb and resource, distinguishing it clearly from sibling tools like get, create, delete, and patch.

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 list verb implies when to use the tool, but no explicit guidance on choosing between this and alternative tools (e.g., get for a single post) is provided. It is clear enough for basic usage but lacks explicit exclusions or alternative mentions.

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