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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description adds the useful facts that it is free, changes nothing, starts no work, and requires read:accounts. It also indicates the saved configuration and revision returned, though return details are limited.

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 three short sentences and is front-loaded with the core purpose. Every sentence adds relevant information about behavior, cost, or permission requirements.

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 read-only status tool with annotations and no output schema, the description covers purpose, side effects, cost, and authorization. The main gap is that it does not explain clientRequestId or clarify the practical difference from soclo_autopilot_read.

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 single parameter clientRequestId has 0% schema description coverage and is not mentioned in the description at all. Although it is optional, the description does not compensate for the missing semantic meaning.

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 names a specific read operation for the saved Autopilot status and identifies the relevant sibling, soclo_autopilot_read. However, saying it returns the same configuration and revision as soclo_autopilot_read leaves the distinction between the two tools somewhat ambiguous.

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?

It gives useful context that the call is free and starts no work, and states the required read:accounts permission. It does not clearly explain when to use status instead of soclo_autopilot_read, and the reference to that sibling may even blur the selection decision.

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