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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the write-profile is covered by structured data. The description adds that generation is instant and driven by 'Agency Workforce v3', but it never clarifies whether the produced post is a draft or a live/scheduled post, nor whether the source idea is consumed — a meaningful gap for a non-idempotent creation tool.

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?

A single front-loaded sentence that states the action and its input sources with no repetition. 'using Agency Workforce v3' is mild marketing filler that adds little decision-making value, which keeps it from a perfect score.

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 annotations present, a full-schema parameter set and no output schema, the description only needs to close the semantic gaps. It does not say what actually gets created (draft vs. published post), whether both source parameters are alternatives or mutually exclusive, or what happens if neither is supplied — real omissions for a generation tool with 0 required parameters.

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 schema already documents all four parameters, giving a baseline of 3. The description contributes one genuinely useful signal — that ideaId and threadId map to two different source types (Idea Bank item vs. Sparring Angle Card) — but adds nothing about the platform or scheduledFor parameters.

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 names a specific verb (convert/turn into) plus both source resources (Idea Bank item, Sparring Angle Card) and the output (a finished single post), which separates it from siblings like generate_posts or create_from_trend. It stops short of explicitly comparing itself to those alternatives, so it lands at 4 rather than 5.

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?

Usage is only implied: the agent can infer it needs a pre-existing saved idea or sparring card, and that publishing/scheduling is a separate step handled by publish_post or schedule_post. There is no explicit when-to-use, when-not-to-use, or named alternative, so this is minimum-viable guidance.

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