gmb_v4_accounts_locations_localposts_delete

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

With annotations already providing destructiveHint=true, idempotentHint=true, and readOnlyHint=false, the description's "Deletes a local post" adds no behavioral context beyond what is already structured. It doesn't disclose whether deletion is permanent, whether it affects associated data, or whether auth is required. It neither contradicts the annotations nor enriches 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 two short sentences with the REST path front-loaded, followed by a plain-language purpose statement. It is economical and avoids waste, though the 'DELETE v4/' prefix is largely redundant with the tool's name and intent.

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 one-parameter delete tool with no output schema, the description covers the essential purpose and parameter pattern, and the annotations handle the behavioral profile. However, it omits context such as what happens on success, whether deletion is reversible, or any caveats about deleting a local post. It is minimally adequate but not rich.

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 for the bare 'name' parameter. The path template v4/{name=accounts/*/locations/*/localPosts/*} does add meaning by indicating the expected resource-name pattern for the parameter. However, it doesn't explain the exact string format beyond the wildcard pattern or any constraints on the name value.

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 states "Deletes a local post," which is a specific verb+resource combination that clearly indicates the tool's function. The REST path template (accounts/*/locations/*/localPosts/*) further clarifies the target resource and helps distinguish this from sibling delete tools like gmb_qanda_locations_questions_delete or gmb_accounts_locations_admins_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 offers no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It simply restates what the tool does without covering when a local post should be deleted, who can perform the deletion, or how this relates to the other localposts tools (create/get/list/patch).

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