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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so safety profile is covered. The description adds genuinely non-structured context: resuming 'authorizes recurring spending under its saved caps' and needs the intelligence:run scope. It does not say what happens to an in-flight run when paused, which is the remaining gap.

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, front-loaded with the action and immediately followed by the consequential side effect. Every clause earns its place with no restatement of the name or title.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. However, for a 4-parameter mutation with zero schema descriptions, the definition omits any parameter mapping and does not state the effect of pausing on an already-running schedule, leaving meaningful gaps.

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% across 4 required parameters, so the description must carry the burden and largely does not. The status enum ('active'/'paused') is only obliquely mapped to 'pause or resume', and brandId, scheduleId, and especially idempotencyKey are never explained or tied to the tool's behavior.

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 pair and resource: 'pause or resume a research schedule', which lets an agent distinguish it from siblings like cancel_research, start_research, and save_research_schedule. It is clear but does not explicitly name which sibling to prefer, so it stops short of a 5.

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?

Usage context is implied rather than stated: the agent can infer this is the toggle for an existing schedule versus cancel_research (terminate) or start_research (initiate). The note that resuming 'requires intelligence:run' is a real precondition, but there is no explicit when-to-use / when-not-to-use guidance or named alternative.

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