yd_campaigns_add

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

No annotations provided. The description does not disclose behavioral traits such as whether the creation is immediate, permissions required, or what the tool returns (e.g., campaign ID). It only states the action without side effects or constraints.

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: first specifies the action, second lists strategies. No fluff. Could include a brief note on return value without harming conciseness.

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?

No output schema, and description does not mention return value or post-creation behavior. For a 15-parameter tool with no annotations, more context is needed about what the tool does upon success or failure.

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 100%, so baseline is 3. The description adds limited value beyond the schema, only listing strategy enum values. It does not explain parameter interactions or conditional requirements (e.g., which fields are needed for specific strategies).

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 clearly states 'Create a new text campaign' which is a specific verb+resource. It distinguishes from siblings like yd_campaigns_update and yd_campaigns_get by the creation action. The list of strategies adds further specificity.

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 explicit guidance on when to use this tool vs. alternatives like yd_campaigns_update for modifications, or yd_campaigns_action for state changes. The description does not mention prerequisites or context for using different strategies.

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