create_flash_price_campaign

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

With no annotations, description fully discloses side effects (auto-activation, price display, overlap considerations) and API details, adding behavioral context beyond the schema.

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?

Well-structured with sections for purpose, use cases, API, return, side effects. Front-loaded and concise without redundancy.

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?

Covers purpose, side effects, return structure, but fails to elaborate on campaign_data parameter structure, which is critical for correct invocation given no output schema and nested object.

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?

Single parameter campaign_data lacks detailed semantic explanation; schema only defines it as an object with additionalProperties, and description only references external structure, leaving agent without guidance on required fields.

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?

Description clearly states tool creates a flash price campaign for limited-time sales, with use cases like holiday sales and clearance. Differentiates from siblings like create_promotion and update_flash_price_campaign by specifying flash sale context.

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?

Provides use cases (holiday, clearance, limited-time) but lacks explicit comparison to sibling tools or when-not-to-use guidance. Implicit differentiation but not explicit.

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