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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral content beyond that: the result is a single status drawn from a fixed set plus a to-do list whose order mirrors the compliance plan's ordered open tasks 'as on the dashboard'. It does not mention the undefined 'Your call' state or whether task entries carry details.

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?

Two compact sentences, front-loaded with the outcome (status) before the supplementary list and the sibling pointer. Given there is no output schema, the enumeration of status values earns its space; no sentence is redundant.

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 one-optional-parameter read tool with no output schema, the description covers what comes back (a status plus an ordered task list) which is the main gap such tools leave. Remaining ambiguity is minor: the 'Your call' status is undefined and it doesn't say how much detail each to-do entry carries.

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 100% and the single 'site' parameter is already fully documented in the schema, including the optional-when-one-site rule and the list_sites pointer. The description adds nothing about the parameter, so the baseline of 3 is appropriate.

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 states a concrete verb and resource (a site's status) and enumerates the exact return vocabulary: 'Checks pass, N fixes needed, Not set up yet, Not checked yet, Your call', plus an ordered open-task list. It also explicitly separates itself from get_task, which 'gives each change', so an agent can tell the two apart without opening either 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?

It gives a clear selecting question, 'am I compliant?', and routes detailed single-item lookup to get_task. It stops short of naming the other plausible alternatives in the sibling set (get_compliance_plan, get_setup_status, get_scan) or stating when this tool is the wrong choice, so an agent must still infer the boundaries.

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