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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds a real behavioral fact beyond them – 'requires read scope' – plus a concrete inventory of what the response contains, which is useful since there is no output schema; it does not cover pagination or run-history depth, but that is minor here.

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?

One front-loaded sentence with the verb and resource first, followed by a compact list of returned data. Slightly awkward that it echoes the tool name verbatim before the colon, but every clause carries information.

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 parameters, no output schema, and annotations covering the read-only safety profile, the description does the needed extra work by enumerating the returned fields and noting the read-scope requirement. An agent can call it correctly and knows what to expect back; only the exact response shape remains unspecified.

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 the baseline applies. The description correctly implies no input is needed; nothing further is required of it.

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+resource ('get autopilot status') and enumerates what the status comprises: configuration state, current config, pending-review count, and latest run step results. That enumeration implicitly separates it from configure_autopilot and run_autopilot_now, but it never names or contrasts those siblings 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?

Usage is only implied: an agent can infer this is the read-side check to call before configuring or triggering a run, but there is no explicit 'use this when...' or 'do not use this for...' guidance, and no alternatives are named.

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