Find feature toggles

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

Annotations already indicate read-only, non-destructive, idempotent behavior. The description adds value by detailing response structure (summary vs. resource body), indicating that heavy fields are in the resource body, and explaining how to dereference the resourceUri for full details.

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?

Description is fairly detailed and well-structured, but slightly verbose. It uses clear sentences and separates purpose, response details, and guidance. Could be slightly more concise, but effective.

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?

Given no output schema, the description adequately explains the return value structure (per-environment state in summary, heavy fields in body, resourceUri for full details). Also clarifies limitations and alternative tools.

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?

Input schema has 100% description coverage. The description does not add new meaning beyond what the schema already provides for parameters. Baseline 3 is appropriate.

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 'customer feature toggles in an Octopus Deploy project'. It distinguishes from siblings by specifying what the tool does not do (creation, deletion, etc.) and references update_feature_toggle for modifications.

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 when to use (listing toggles with per-environment state) and when not to use (for creation, deletion, renaming, rollout-group management). Mentions update_feature_toggle as the alternative for flipping toggles.

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