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

Annotations offer minimal information (readOnlyHint=false, destructiveHint=false). The description adds meaningful behavioral context by explaining what the autopilot does when enabled and the API key requirement, which helps the agent understand the tool's side effects and prerequisites.

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 only two sentences with no fluff. The first sentence states the core action, and the second adds essential context and a requirement. This is an ideal structure for a simple tool.

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 simple two-parameter toggle with no output schema, the description covers purpose, behavior, and a prerequisite. It does not discuss return values or potential side effects beyond enabling automation, but these are secondary for this tool's simplicity. The main gap is the absence of alternative tool guidance, but that is a minor issue.

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%, but the parameter names are self-explanatory. The phrase 'site's autopilot on or off' maps to siteId and enabled, providing basic semantics. However, no explicit parameter-level detail is added, so it does not fully compensate for the lack of schema descriptions.

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 clear action ('Turn a site's autopilot on or off') and defines what autopilot means ('Spook plans, writes, and publishes articles automatically'). This distinguishes it from sibling tools like generate_article or publish_article, which handle specific content steps rather than a site-wide automation toggle.

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 description gives clear context for when to use it (when toggling site-wide automation) and mentions a prerequisite (requires an agent API key). It does not explicitly name alternatives or exclusions, but the context is unambiguous.

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