setBulkCallDailyTimeControl

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the description carries the burden of explaining what the mutation does. It adds useful nuance: 'holds rather than finishing' and 'resumes the next day.' However, it does not disclose whether it overwrites existing settings or any side effects on in-progress calls, which are relevant 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 two sentences with high information density. The purpose is front-loaded, and the behavioral consequence is stated immediately. No filler or redundant phrasing. The '(Tags: Bulk calls)' line is minor and does not harm 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?

Given the full schema coverage and absence of an output schema, the description adequately conveys the tool's purpose and behavioral effect. It could mention that the tool can also disable the daily window (since booleans exist), but this is implicitly covered by the schema. The description is sufficient for correct invocation.

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%, and every parameter is already documented with clear descriptions (e.g., 'Hour of day to stop, 0 to 23. Fractions are allowed'). The tool description adds no additional parameter-level meaning, so the baseline of 3 applies.

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 a specific verb ('Restrict') and resource ('a campaign') and immediately clarifies the behavioral effect: calls hold outside the window and resume next day. This clearly distinguishes it from other setBulkCall* tools (e.g., concurrency, number active) without needing to open the schema.

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 is given on when to use this tool versus alternatives, such as 'Use this when you need to set calling hours; for concurrency use setBulkCallConcurrency.' The description only explains what it does, not the decision context. Given many sibling tools, this is a notable gap.

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