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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the description is not solely responsible for those traits. It adds meaningful behavioral context: the block is account-wide across every campaign, there is no per-campaign holiday, and the action is reversible via holiday_delete. It does not cover permissions, timezone handling, or effects on already-scheduled outreach.

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 short and front-loaded with the primary action. Each sentence earns its place by clarifying account-wide scope, routing to alternatives, or noting reversibility.

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 one-parameter mutation with annotations and no output schema, the description covers the essential scope, alternatives, and reversibility. Minor gaps remain around timezone interpretation and what happens to already-scheduled messages on the blocked date.

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% for the single blockedAt parameter, and the schema already explains that the date may be epoch milliseconds or ISO 8601. The description only refers generally to a 'given date' and does not add format or timezone semantics beyond the schema.

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 action and resource: stopping all outreach on a date across every campaign. It explicitly distinguishes this from per-campaign and per-lead stopping, so the agent can separate it from siblings like campaign_set_status and lead_update.

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?

It gives explicit when-to-use guidance and names the alternatives for narrower scopes: campaign_set_status with PAUSED for one campaign and lead_update for one lead. It also names holiday_delete as the reverse operation, leaving little ambiguity about tool selection.

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