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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, and idempotentHint=false. The description adds essentially nothing beyond that safety profile -- notably it never explains that a mandatory idempotency_key exists (despite idempotentHint=false) or what happens on duplicate submission.

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 well-formed sentence with no filler and the core action front-loaded. It is efficient, though arguably too short for a 10-parameter mutation tool.

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 creation tool with 10 parameters, nested free-form objects, and a required idempotency_key, the description omits prerequisites, workspace scoping, and any behavior on retries. With annotations covering only the safety profile, the definition leaves significant gaps.

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 only 70% across 10 parameters, and the description merely restates the 'initial body or topic' idea that the schema already documents via initial_body and seed_topic. It does not compensate for the undocumented remainder (e.g. brand_id, tags, query overrides).

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 (Create) and resource (idea on the workspace's idea board) with the seeding option, which is enough to separate it from create_draft or create_post. It does not explicitly contrast with sibling creation tools, so it falls short of a 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?

The description gives no when-to-use guidance, no mention of the required idempotency_key, no note that workspace_id is required for content creation, and no routing to alternatives like create_draft or create_post. An agent must infer all of this from the schema.

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