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

Annotations already declare the write/destructive/open-world profile, but the description adds the crucial consequence that this 'creates an externally visible social post' — meaning the effect leaves the system and is publicly visible. It still omits retry/idempotency behavior and any rate-limit context.

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?

Two short sentences, front-loaded with the primary action and then the scheduling condition; no filler. It is efficiently sized, though it stops short of using that compactness to convey more essential detail.

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 an 8-parameter destructive external-publish tool with 13% schema coverage and no output schema, the description is too thin: it never mentions required identifiers, the idempotency key, connection targeting, or what a successful publish returns.

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 only 13% (just aiGenerated), so the description must compensate, yet it only explains scheduledAt's effect. brandId, pieceId, connectionIds, caption, hashtags, and idempotencyKey receive no added meaning anywhere.

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?

States a specific verb and resource (publish a rendered content piece) and adds the scheduling variant, so the action is unambiguous. It does not explicitly contrast itself with the sibling publish_clip, so the agent must infer the piece-vs-clip distinction from the tool name.

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?

Gives one clear conditional: schedule by supplying scheduledAt. There is no guidance on when to prefer this over publish_clip, nor on prerequisites (piece must be rendered) or when not to use it.

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