gmb_v4_accounts_locations_localposts_create

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

Annotations already indicate readOnlyHint=false and idempotentHint=false, so the write nature is disclosed. The description adds the HTTP method and path but no additional behavioral context (e.g., visibility of the post, validation rules, or side effects). It does not contradict the annotations, so it meets the baseline but adds little beyond them.

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 sentence that front-loads the HTTP method and path before stating the action. It is efficient with no filler words, earning a high score.

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 has no output schema and the description does not mention the response format or the content of the request body. For a create operation, the agent lacks details about what constitutes a valid local post and what to expect back, making the description incomplete despite the low parameter count.

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 only 50%; the `parent` parameter is clarified by the REST path template in the description, but the `body` parameter is only described generically as 'JSON request body' with an `x-google-schema-ref` to `LocalPost`, and the description does not explain what fields a local post requires. With 50% coverage, the description should compensate more but only partially does.

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 uses the specific verb 'Creates' and identifies the resource as 'a local post for a location', with the REST path template `v4/{parent=accounts/*/locations/*}/localPosts`. This clearly distinguishes it from sibling operations like `localposts_list`, `localposts_patch`, and `localposts_delete`.

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 for creating a new local post but does not explicitly state when to use it versus alternatives (e.g., using `localposts_patch` for updates). No exclusions or alternative tools are mentioned, leaving the agent to infer from the verb and resource name.

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