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

Annotations already declare this a safe, idempotent read, so the description's job is to add scope detail — and it does, stating that archived flags are excluded unless includeArchived is true, which is a real filtering behavior not visible in annotations. It also discloses the shape of each returned item, though it says nothing about ordering or result size.

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, no filler, with the returned-content summary placed first and the important exclusion rule second. Every sentence carries information an 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?

With no output schema, the description usefully previews what each flag record contains and explains the archived-flag default, covering the main behavioral questions for a read-only list tool. Only minor gaps remain, such as pagination or ordering behavior for large flag sets.

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 coverage is 67%: app and environment are documented in the schema, but includeArchived has no schema description. The description supplies the missing default semantics for includeArchived, but contributes nothing about the app or environment parameters beyond what the schema already explains.

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 the resource (feature flags) and enumerates what each entry carries — per-environment enablement, rollout percentage, targeting rules, variants — which clearly separates it from sibling tools like upsert_flag or get_app. The verb 'list' is only implied by the title rather than stated in the description itself, keeping it just short of 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?

There is no guidance on when to choose this over list_apps, get_app, or upsert_flag, nor any prerequisite or exclusion statement beyond the archived-filter note. The agent must infer usage from the resource name alone.

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