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

Annotations declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the write/side-effect profile is partly covered. The description adds the quota requirement, which is genuinely useful behavioral context. But it omits the most consequential fact for an agent: whether the generated post is saved/returned only, or also affects the account, which matters enormously next to publish-post and create-post siblings. It also doesn't mention the external AI call implied by openWorldHint.

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?

Three short sentences, front-loaded with the purpose, then the precondition, then the return. No filler, though the opener slightly restates the title 'Generate post with AI'.

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?

With four parameters and no output schema, the description is serviceable but thin: it says 'Returns the generated post' without saying whether that post is persisted, and with siblings named create-post, refine-post, and publish-post, the lifecycle position of the generated artifact is exactly what an agent needs. The quota note partially compensates.

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%, and the parameter descriptions already explain prompt, isThread (X-only vs LinkedIn behavior), platform defaults, and profileId defaults. The description adds nothing beyond that, so the baseline 3 is appropriate.

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 plus the generation mechanism ('Generate a new post using AI based on a prompt'), which is clearer than a bare tautology. However, it never distinguishes itself from the sibling create-post or refine-post, so an agent cannot tell from the description alone whether generating is the same as creating or whether the result is persisted.

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?

It gives one real precondition — 'Requires usage quota' — which tells the agent a metered action is involved. But there is no when-to-use guidance relative to create-post, refine-post, or publish-post, and no indication of when-not to call it.

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