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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds critical non-annotation context: output is text only, nothing is stored, the copy is lost unless saved, and provider/Publish-permission prerequisites apply.

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-loads purpose and follows immediately with the persistence warning and prerequisites. Each sentence adds actionable information; there is no 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, so the description's 'Returns text only' is essential and present. It also covers persistence, the follow-up tool, provider connection requirements, and plan permissions, leaving no major gap for calling correctly.

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%, with both `prompt` and `provider` documented. The description adds provider-connection context, but the schema already notes providers are connected in the web app, so it does not significantly extend parameter semantics.

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 action ('Generate LinkedIn post copy'), resource, and input source ('from a prompt using a connected AI provider'). It also names `post_upsert` as the saving sibling, making the drafting-vs-persistence distinction clear.

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?

Explains that the tool returns text only and stores nothing, and explicitly directs the agent to `post_upsert` or the copy is lost. It also gives prerequisites (connected AI provider, Publish permission). It does not compare against other AI-drafting siblings, but usage context is clear.

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