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

The description is consistent with the annotations: readOnlyHint=false marks this as a write operation, and publishing to a connected social platform conveys an external side effect. However, it does not disclose irreversibility, credit spending, or the need for explicit confirmation, though the _confirmed parameter's schema note partially covers that requirement.

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, front-loaded sentence with no filler or restatement of the full schema. It conveys the core action clearly and economically.

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?

This is an external, side-effecting publish action with five parameters and no output schema, yet the description omits expected result, confirmation workflow, default platform behavior, and preconditions. The _confirmed parameter is visible in the schema, but the tool-level description alone is too thin for an agent to safely invoke a credit-spending publish call.

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 100%, so the baseline is 3 even though the description adds no per-parameter details. The phrase 'one GTM content item' and 'connected social platform' lightly reinforces contentId and platform intent but does not explain how pageId, igUserId, or platform override interact.

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 a specific action — 'Publish one GTM content item to a connected social platform' — with a clear verb, object, and destination. This differentiates it from the generation, listing, and analytics sibling tools without needing to name them.

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 gives no guidance on when to use this tool versus alternatives or what workflow should precede it. It does not mention that publishing should follow content generation/review, nor does it provide exclusions or conditions around platform targeting or user confirmation.

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