list_feature_flags

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

No annotations are provided, so the description bears the full burden. It discloses that the operation is a read-only list and requires the 'feature-management:features:read' scope, which is useful. However, it does not describe return format, pagination, or ordering, leaving gaps.

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 very concise, with a single sentence plus the scope requirement front-loaded. Every word is relevant, though it could potentially be merged for slightly better flow.

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?

The tool has 2 required parameters with full schema coverage, but no output schema. The description lacks details on what the response contains (e.g., list of flag objects) and any limitations. It is adequate for a simple list tool but not fully complete.

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 100% with clear parameter descriptions. The tool description adds no extra meaning beyond what the schema provides for 'projectKey' and 'featureKey', thus meeting the baseline expectation.

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 states the verb 'List' and the resource 'all flags in a feature', specifying the API and required scope. It effectively distinguishes from sibling tools like 'get_feature_flag' (single flag) and 'list_features' (features in a project).

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 does not provide when-to-use guidance or explicitly mention alternatives. While it hints at usage context by naming the API and required scope, it lacks a clear statement like 'Use this to get all flags for a feature; for a single flag, use get_feature_flag.'

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