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

With no annotations, the description carries the behavioral disclosure burden. It does well by stating there is no input, describing the returned fields, and explicitly noting that this tool returns only a list with no verdict because the server runs none of the checks. This conveys important non-obvious behavior beyond a simple enumeration.

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?

Three short sentences, each earning its place: what the resource is, when to use it, and what it returns. The key behavioral caveat ('no verdict') is saved for the end but is clearly stated without padding.

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 zero-parameter list tool with an output schema, the description is complete. It explains the provenance, the practical use, the return shape, and the critical limitation that no checks are actually run by this server. Nothing essential is missing.

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?

There are zero parameters, so the schema provides no meaningful parameter semantics. The description explicitly confirms 'No input', which matches the empty schema and leaves no ambiguity for the agent.

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 clearly identifies the resource: the checks that the model's own gate runs, sourced from the checker release of the server. It also explains the intended use—seeing which rules a script enforces—which separates it from a generic list. It does not explicitly name a sibling alternative, but the content is specific enough to avoid confusion.

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?

The description gives a clear usage context: use this to see which rules a script enforces and which are left to a reader. It does not provide explicit exclusions or name alternative tools for other cases, but the 'Use to...' phrasing gives practical direction.

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