create_campaign_budget_schedule

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a write operation ('create') but doesn't disclose permissions needed, rate limits, whether the schedule is reversible, or what happens upon success/failure. This is inadequate for a mutation tool.

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 a single, efficient sentence with no wasted words. However, it's overly concise given the tool's complexity—front-loaded but lacking necessary detail for a 6-parameter mutation tool.

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 mutation tool with 6 parameters, 0% schema coverage, no annotations, and sibling tools present, the description is incomplete. It doesn't clarify the tool's role in the ecosystem, behavioral expectations, or parameter meanings, despite an output schema existing.

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 0%, so the description must compensate but adds no parameter details. It doesn't explain what 'budget_value_type' means, the format of 'time_start'/'time_end', or the purpose of 'meta_access_token'. This leaves all 6 parameters poorly understood.

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 states the action ('create') and resource ('high-demand budget schedule for a campaign'), which is clear but vague. It doesn't specify what makes a schedule 'high-demand' or differentiate from sibling tools like 'create_campaign' or 'update_campaign' that might also involve budgets.

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 guidance on when to use this tool versus alternatives is provided. There's no mention of prerequisites, timing considerations, or how this relates to sibling tools like 'create_campaign' or 'update_campaign' that might handle budgets differently.

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