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

Annotations only cover safety hints (readOnly false, idempotent true), so the description carries the real burden and delivers: it discloses that one mode spends credits, that weekly_quota is plan-capped, and that auto-publishing is refused here with a redirect to the app. These are exactly the side-effect details an agent needs before invoking a settings mutation.

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?

Leads with the purpose, then spends two dense sentences on mode semantics; every clause carries decision-relevant information. The mode enumeration is compact but the parenthetical explanations make the second sentence heavy.

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?

Output schema exists so return values need no explanation, and the description covers the costly/irreversible aspects plus the unsupported mode. It does not state that omitted parameters leave current settings unchanged (0 required params), which matters for a partial-update tool.

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 coverage is only 33% (only mode is documented in the schema), so the description compensates by defining each mode's cost/review behavior, noting weekly_quota is plan-capped, and explaining paused toggles the scheduler. 'paused pauses or resumes' is slightly circular and the quota's 1-7 bound is left to the schema, but coverage is meaningfully improved.

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?

States a specific verb and resource ('Change the workspace's content autopilot'), which cleanly separates it from the read-only sibling get_autopilot. The follow-on sentences enumerate the exact modes so an agent knows the decision space before opening the schema.

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?

Gives real selection context for each mode: draft_only 'spends nothing' versus requires_approval which spends credits and holds drafts for review, plus an explicit exclusion (full_auto cannot be set here, use the Rankwise app). It stops short of naming the sibling to call for reading current settings, so it is clear context without full alternative routing.

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