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

Annotations already declare non-read-only, non-idempotent, non-destructive. The description reinforces non-idempotency with a concrete consequence ('calling twice creates the cards twice') and adds facts annotations cannot express: ordering behaviour (created in order at the bottom of their column), no publishing, and the return payload/url semantics.

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?

Three dense sentences, front-loaded with the core action and limits. Every sentence carries information (scope, item shape, side effects, return value), with only mild redundancy between 'not idempotent' and the annotation.

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 supplies the return shape { contents, created } and explains the URL, and it covers limits, required fields, ordering, and idempotency. The only gap is the unmentioned optional brandId parameter.

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?

With 0% schema description coverage, the description compensates well by enumerating the item shape and stating 'title or idea required' plus the optional fields. It omits brandId entirely, which is the one parameter left undocumented in both description and schema.

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 with batch scope ('Create 1-20 content cards in one call (no AI)'), which clearly separates it from the singular create_content and the AI-driven creation paths. It does not name those siblings explicitly, so the differentiation relies on the agent inferring from the name.

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 clarifies what does NOT happen ('nothing is published') and the non-idempotent consequence, which is useful context. However, it never says when to prefer this over create_content or create_content_from_source, nor any prerequisites, so usage is only implied.

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