list_flag_definitions

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

Warns that full definitions are large and that 'summary: true' avoids oversized responses. No annotations provided, so description carries full burden; it addresses size/performance but not auth or side effects.

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 efficient sentences, front-loaded with action and resource. No wasted words.

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?

Sufficient for a list tool: explains output variability (full vs summary). No output schema provided, but description gives a reasonable expectation. Could mention pagination behavior but not critical.

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%, baseline 3. The description adds value for the 'summary' parameter (purpose and benefit). Other parameters are not elaborated beyond schema, but that is acceptable given full coverage.

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?

Clear verb ('List') and resource ('feature flag definitions') are stated. The description distinguishes from 'get_flag_definition' (singular) and 'list_feature_flags' (different resource) by specifying scope and the summary option.

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?

Provides explicit guidance on using the 'summary' parameter to reduce payload size when only identifying flags. Does not explicitly list when not to use, but sibling tools provide context for alternatives.

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