Find feature toggles

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds: summary contains per-environment state, heavy fields are in resource body, and what operations are not exposed. No contradiction, and valuable context beyond annotations.

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?

Concise, well-structured description. First sentence states purpose clearly, followed by details on response structure, dereferencing, and usage boundaries. Every sentence adds value, no redundancy.

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?

Despite no output schema, description thoroughly explains what the response contains (summary with per-environment state, resourceUri for heavy fields). Also covers limitations (no create/delete) and pagination details. Complete for a list tool with good annotations.

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?

All parameters have schema descriptions (100% coverage). Description adds specifics: 'Case-insensitive substring match' for partialName, 'canonical tag names' for tags, and matching logic for tags and environmentIds. Also explains pagination and result structure, enhancing understanding beyond the schema alone.

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?

Clearly states 'List customer feature toggles in an Octopus Deploy project' with specific verb and resource. Distinguishes from sibling tools like update_feature_toggle and lists exclusions (no create/delete).

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 directs use of update_feature_toggle for modifications and refers to UI for unsupported operations. Also instructs to dereference resourceUri for full details. Provides complete context for when to use this tool vs alternatives.

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