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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the mutation profile is covered. The description adds genuinely new context beyond the annotations: the run consumes/meters points and the output is written to the event log rather than returned.

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?

Front-loaded and short, but the cost point is stated twice: 'Uses points. (uses points, metered on the models used like the website)'. The parenthetical restates rather than adds, wasting the most valuable position in the description.

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?

With no output schema, the description correctly tells the agent the result lands in the event log, and it flags the point cost. Since the required 'agent' enum is undocumented and no sibling alternative is named, it stops short of being sufficient for confident invocation.

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 50% (autopilot_id documented, the agent enum is not), and the description adds no meaning to either parameter — it never explains the indicator/intelligence/fundamental/decision values. It only gestures at 'the models used', which is not tied to a named parameter.

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 ('Run one of the autopilot's agents now, outside its schedule') and notes where the result goes. The 'outside its schedule' qualifier implicitly distinguishes it from start_autopilot, though it never names the sibling explicitly.

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 an implied trigger ('now, outside its schedule'), which tells the agent this is an on-demand run rather than a scheduled one. It never states when to prefer start_autopilot or autopilot_action instead, leaving the routing decision to inference.

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