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

Annotations only provide readOnly/idempotent/destructive hints. The description adds real behavioral detail: pausing stops future scheduler-dispatched runs but not manual trigger_agent_activity calls, in-flight runs are unaffected, and the operation may trigger a sensitive multi-step approval flow with from-now-on vs just-once approval semantics. This goes well beyond the structured fields.

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 organized into three compact paragraphs with distinct jobs: what it does, when to use it, and approval behavior. There is no filler, though the sensitive-tier bracket is slightly dense and could be tightened without losing meaning.

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 sensitive mutation tool with no output schema, the description covers the required action, scope, exceptions, routing conditions, and approval flow. Combined with the fully documented schema, an agent has everything needed to select and invoke the tool correctly.

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%, so the schema already documents all four parameters. The description mostly restates that activity_name is optional, scopes to a single activity, and omitting it affects the whole plan — all already present in the schema, so no additional semantic value is added.

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 opening sentence names the exact action ('Pause or resume') and the resource ('an agent's scheduled activities'), and scopes it to the whole activity plan vs a single activity via activity_name. It also implicitly distinguishes itself from trigger_agent_activity by noting manual triggering still works, and from deactivate_agent by limiting scope to scheduled activities.

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?

The 'Routing:' paragraph gives concrete conditions: pause for a misbehaving/low-quality agent, single activity, or maintenance; resume after recalibrating the JD/skills or fixing the issue. It does not explicitly state when not to use this vs alternatives like deactivate_agent, so it stops short of full exclusion guidance.

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