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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, destructiveHint=false, so the safety profile is largely covered. The description adds meaningful context beyond annotations: it documents the per-flag fields returned (including 'warnings' on suspicious flags), notes it lists 'every' flag in the app, and explains edge-case semantics (numbers are plan quotas, permission on a record stays in app code). It doesn't state pagination or limits, which would be useful for a list-all tool, so not a 5.

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 front of the description is tight and useful (purpose, fields, when-to-use, alternatives). However it then drifts into a lengthy conceptual primer about flags vs privileges vs roles vs plans vs quotas, which is better suited to the referenced integration guide than the tool definition, diluting conciseness.

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 read-only list tool with a single optional param, full schema coverage, and no output schema, the description gives enough to call it correctly: what is listed, what each entry contains, and when to choose it over siblings. The only material gap is list behavior (ordering, pagination, size limits).

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?

Only one optional parameter (`app`), and schema description coverage is 100% — the schema already says to omit it to use the current app. The description doesn't add syntax about `app`, but with a single well-documented optional param, the baseline is high; the description's mention of 'the Bridge app' contextualizes scope without repeating the schema.

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 specific verb (List) and resource (feature flags), scoped to the 'Bridge app', and enumerates the returned shape (key, description, lifecycle state, value type, targeting rule tree, scheduled transition, source, warnings). This makes it clearly distinct from get_flag (single flag), create_feature_flag, and update_feature_flag.

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?

Explicitly says when to use it ('verifying a flag key exists before referencing it in code, or inspecting targeting before relying on a flag') and names alternatives for adjacent jobs: get_app/get_auth_config for app-level auth/config, get_environment_info for project wiring, and get_integration_guide topic=fit-together for the full rule.

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