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

Beyond the annotations, the description explains the flag vocabulary, the meaning of ok=false, the default failOn values, and that an unknown provider is status unknown rather than an error. It also clarifies that retirement_announced is warning-only and that require checks sourced security records, which is substantive behavioral context.

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 dense but front-loaded and contains no obvious filler; each clause carries flag or gating semantics. Its long single-paragraph enumeration of flags makes it less structurally scannable than it could be.

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?

There is no output schema, but the description explains the key return semantics: per-provider flags, ok=false behavior, default failOn, and unknown handling. The main remaining gap is the undocumented jobs parameter.

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?

With 0% schema description coverage, the description must carry parameter meaning. It successfully explains failOn, require's enum values, and the provider context, but it never directly documents the jobs parameter, so coverage is only partial.

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 specific action ('Flags for each provider in a stack') and a clear gate outcome ('ok=false when a provider has a flag in failOn'), so the core purpose is legible. It does not explicitly distinguish this tool from close siblings such as stack, coverage, or compare, which keeps it below a 5.

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 title and the failOn/ok=false behavior imply this is a CI gate, giving an agent an implied usage context. However, the description never explicitly says when to use this versus siblings, nor does it name alternatives or exclusions.

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