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

Annotations already indicate this is not read-only, is idempotent, and not destructive. The description adds the account-scope and optional media selection, which is helpful. However, it does not disclose side effects such as whether the idea is marked as used, what happens to the idea after conversion, or what the return value is. With annotations lowering the bar, this is minimally adequate but not rich.

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 compact sentences with the primary action and key optionality front-loaded. No filler or repetition, making it easy to scan.

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 a tool with two parameters and no output schema, the description covers the core action but omits important practical details: it does not state whether the tool returns the new draft post, what happens to the original idea, or any prerequisites beyond having an idea ID. An agent may be uncertain about the outcome, which is a notable gap given annotations do not clarify return behavior.

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 coverage is 0%, so the description must compensate. The only parameter-specific information is that mediaAssetIds is an optional subset from the idea's media pool. The ideaId is not explained beyond being an identifier of an idea, and no guidance is given on how to obtain it or its validity. The description adds minimal context beyond the schema's field names.

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 uses a specific verb ('converts') and direct resource ('idea to draft post'), and specifies the account context. It clearly distinguishes from generic post creation by tying it to an existing idea, and the optional media subset is mentioned, giving a complete picture of the tool's function.

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?

No guidance is provided on when to use this versus sibling tools like create_post or update_idea. It does not state prerequisites (e.g., idea must exist, belong to user) or exclude scenarios where this tool is inappropriate. The usage context is only implied, not explicit.

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