Get Feature Flag (Admin)

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds no extra behavioral context beyond what annotations and schema provide, such as return format, error handling, or admin permission requirements. It does not contradict the 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?

The description is a single, concise sentence that conveys the essential operation without any fluff. It is appropriately sized for a simple get tool and every word is relevant.

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 simple single-fetch tool with complete schema and safety annotations, the description is adequate but has gaps: it does not describe the return value (no output schema exists), behavior on missing keys, or any admin-specific implications beyond the title. These gaps make it minimal 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 the single required parameter 'key' described as 'Feature flag key'. The description's mention of 'by key' adds no new meaning. Baseline 3 is appropriate since the schema fully documents the parameter.

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 'Fetch a single feature flag by key' clearly states the action (fetch), the resource (feature flag), and the scope (single by key). It distinguishes itself from sibling list/get tools like lyzr_list_feature_flags_admin and lyzr_get_feature_flags by indicating a single-item retrieval.

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 provides no guidance on when to use this tool versus alternatives. While 'by key' implies a single lookup, it does not explicitly say to use this instead of list_feature_flags_admin or note any prerequisites or admin permissions implied by the title.

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