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

Beyond annotations (non-read-only, non-destructive, non-idempotent), it discloses real constraints: Google posts take text and at most one photo, button URLs must be https, CALL uses the listing phone, and offers may only use owner-supplied price/coupon/deadline values. It does not say whether a second call replaces or merges prior options, which matters given idempotentHint=false.

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?

Front-loaded with the action and then the option inventory; nearly every clause adds information. The single long sentence listing all option types is somewhat dense but avoids filler.

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?

No output schema exists, and the description supplies scope, allowed values, and the key content constraints needed to call a nested-object mutation correctly. Gaps remain around date string format, replacement vs merge semantics, and what happens if the target is not a Google destination.

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?

With only 50% schema description coverage, the description carries most of the load: it enumerates topicType values, the five URL-bearing CTA types with the CALL exception, and the event/offer subfields, all of which are undescribed in the schema. It leaves out date/time formats and the 58-char title limit, so it does not fully compensate.

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 opening clause states a specific verb and scope — set Google-only options on a scheduled post's Google destination — and identifies target_id's origin (the post's targets), which distinguishes it from schedule_social_post and update_social_post.

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 phrase 'scheduled post's Google destination' implies the precondition (post already scheduled, Google target exists), but no sibling is named and no explicit when-not guidance is given — e.g., whether this is needed before or after queueing for publishing, or how it relates to prepare_google_change.

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