add_content_ideas

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

With no annotations at all, the description carries the full burden, and it does disclose two real behavioral facts: the operation is a batch insert and it caps at 50 items per call, and inserted items land in the IDEA stage. It omits what matters most for an unannotated write tool — duplicate handling, partial-failure semantics, permission requirements, and whether IDEA is a starting stage that can be advanced.

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 sentences, front-loaded with the verb, resource, destination, and stage; the batch cap sits in the second sentence where it belongs. No filler and nothing restating the title.

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?

There is no output schema, yet the description says nothing about what an insert returns (created IDs? count? per-item errors), which an agent needs to chain into update_content_progress. The pipeline framing is present but the surrounding workflow — what 'IDEA stage' implies for subsequent calls — is left implicit.

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%, including descriptions for the nested idea object fields and the optional accountId/workspaceId, so the schema already does the explanatory work and baseline 3 applies. The description adds only the 50-item ceiling on `ideas`, which is genuinely useful but is the sole semantic addition.

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 ('Batch adds new content ideas/plans') plus the exact target and resulting state ('SocialDispatch pipeline queue in IDEA stage'), which no sibling does — list_content_pipeline and update_content_progress operate on items already in the queue. An agent can distinguish this from generate_social_content (which generates copy) at a glance.

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?

'Allows brainstorming and researching batches of content ideas (up to 50 at once)' implies the up-front ideation phase, but never states when to use this versus generate_social_content or how it relates to update_content_progress / get_next_pipeline_item downstream. Usage is inferred rather than prescribed; no exclusions or preconditions (e.g., required workspace context) are given.

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