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

Adds real behavioral context beyond the annotations: required scope (write:status), a prior-enrollment prerequisite, and a data-hygiene constraint ('Never include prompts, credentials or error text'). It does not, however, explain the destructiveHint=true / idempotentHint=true profile — presumably the report overwrites previously recorded counters — and the assurance that it does not 'change limits' sits in mild tension with a destructive annotation.

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?

Four short, front-loaded sentences with zero filler: purpose first, then preconditions, then negative scope, then the data-hygiene rule. Every clause carries information the agent needs.

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 write-scoped tool with no output schema it covers prerequisites, limits of authority, and data hygiene well, which is what the annotations cannot express. It is incomplete at the payload level: with 8 required-ish fields and no schema descriptions, the agent gets no guidance on valid enum values, counter semantics, or the relationship between day and the counters.

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% across 8 parameters, including two enums (state, last_error_code) and a strict date pattern for day, yet the description explains none of them. The phrase 'status and daily counters' only loosely gestures at the payload shape and gives no meaning for any individual field such as next_check_at or last_error_code.

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 concrete verb (report) plus the resource and its scope ('bounded private runner status and daily counters'), and explicitly distances itself from sibling behaviors such as acknowledging inbox items. An agent can tell what it writes and what it is not for without 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 clear preconditions ('Requires write:status and prior Autopilot enrollment') and a set of explicit non-uses (does not grant authority, change limits, acknowledge inbox items, or prove reported model use), which effectively routes the agent away from siblings like acknowledge_inbox and set_follow. It stops short of naming a specific alternative tool or a positive trigger scenario, so it is not a full when/when-not map.

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