Create a local post

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

Annotations already set readOnlyHint=false and idempotentHint=false, but the description adds the return state (usually PROCESSING before LIVE), the rate limit, and the legacy-v4-API restriction. This goes beyond annotations and does not contradict 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 dense paragraph, front-loaded with the action and then systematically covering return format, ALERT restrictions, rate limits, and API scope. Every clause earns its place; no filler or schema repetition.

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?

Given the complex nested LocalPost object and three required parameters, the description is thorough: it discloses the return value with state, warns about ALERT rejections, and informs about rate and API-version constraints. This is complete for a successful invocation.

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?

While schema coverage is 100%, the description explains the nested `post` object fields in detail: topicType options, callToAction structure, required event/offer fields, and media format. This significantly helps construct a valid request beyond the schema's brief example.

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 'Publishes a new local post on the Business Profile' with a specific verb and resource. This clearly distinguishes it from sibling tools like list_local_posts, update_local_post, and delete_local_post by focusing on creation.

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 explicitly warns that ALERT posts are restricted to Google-initiated campaigns and are typically rejected, and notes that local posts exist only on the legacy v4 API. It also mentions the 10 edits/min rate cap, providing clear when/when-not context.

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