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

Beyond the annotations (which only say it is not read-only and not destructive), the description discloses the concrete side effects (insights refresh plus discovery top-up), the skip behavior for steps already completed today, a hard rate limit of 2 per hour, and the required generate scope. That is exactly the operational context annotations cannot carry, and none of it contradicts the supplied hints.

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?

Three short sentences, each earning its place: what it does, how it handles already-completed work, then the operational limits. The core action is front-loaded and there is no filler or repetition.

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 parameterless mutation with no output schema, the description covers everything an agent needs before calling: what executes, that prior completed steps are skipped, the 2-per-hour cap, and the auth scope requirement. Nothing material is left out, and return-value detail is not required here.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond what the empty object schema already shows; the baseline for a parameterless tool applies. The description correctly spends no words on parameters and uses the space for behavior instead.

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 gives a specific verb and resource ("queue a manual autopilot run") and clarifies scope with the parenthetical "insights refresh + discovery top-up on the standing campaign." It implicitly contrasts with scheduled autopilot runs, but never names configure_autopilot or get_autopilot_status, so an agent must infer the boundary from those siblings' own definitions.

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?

"Manual" and "immediately" imply this is the on-demand trigger as opposed to the scheduled path, which gives some usage context. There is no explicit statement of when to prefer this over configure_autopilot or get_autopilot_status, and no stated prerequisites beyond scope, so guidance is implied rather than spelled out.

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