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

The description discloses traits beyond the annotations: it consumes credits, requires a completed brand profile, persists output as a research session, and defines what an idea contains. The annotations only say it is a non-destructive write, so the description adds substantial behavioral context.

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?

The description is three dense sentences with no waste. The core action, the cost warning, the prerequisite, and the carousel exception are all front-loaded and 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 non-destructive write tool with no output schema, it covers prerequisites, cost, persistence, and output contents well. It does not explicitly describe the return value or default behavior for limit/platforms, which keeps it just short of fully complete.

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 all four parameters are already documented in the schema. The description adds little parameter-specific meaning beyond mentioning topic and the carousel routing, so the baseline of 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?

The description gives a specific verb and resource ('Generates on-brand post ideas') and enumerates the produced fields (hook, caption, hashtags, image prompt, format). It also explicitly distinguishes itself from create_carousel and generate_image for carousel-format ideas.

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 names the prerequisite ('Needs a completed brand profile'), warns about credit cost, and routes a specific scenario (carousel-format ideas) to create_carousel rather than this tool or generate_image. That gives the agent clear conditions for use versus alternatives.

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