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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description discloses the fan-out behavior — one draft per snapshot per connected platform — and confirms the output lands in the draft queue rather than being published. It stops short of warning about duplicate creation on repeat calls, which the non-idempotent hint implies.

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?

One front-loaded sentence naming the transformation, the fan-out, and the destination, plus a short safety clause. No filler and every clause carries information.

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 no output schema, the description helpfully names list_drafts so the agent knows how to retrieve the created drafts. It does not say what the call itself returns (e.g., created draft identifiers), which is the one remaining gap for a creation tool.

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 single parameter is already documented as '1–3 trend snapshot UUIDs — from get_trends.' The description restates the same bound and provenance without adding format or syntax detail, so the baseline 3 applies.

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 ('Turn 1–3 trend snapshots into draft posts') with the source (get_trends) and destination (draft queue / list_drafts) named. It clearly distinguishes itself from schedule_trend_posts and generate_trend_platform_content by declaring that nothing is scheduled or published.

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 says when to use it (when you hold 1–3 snapshots from get_trends) and implicitly excludes the scheduling sibling by stating nothing is scheduled or published. It does not name an alternative explicitly, so it falls just short of a 5.

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