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

Annotations only declare readOnlyHint=true. The description adds real behavioral detail beyond that: it returns the conditional expression/rules instead of a resolved value, and it explains the partial-context tolerance when the schema demands a context arg. The response-shape disclosure is genuinely useful for an inspection tool.

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?

Three sentences, lead sentence front-loads the core distinction, and the GraphQL example is compact. Minor redundancy between 'without reducing them' and 'with no context', but nothing wasteful enough to impede scanning.

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?

No output schema exists, yet the description covers what is returned (conditional expression/rules), how the selection maps under root, and how context is handled. For a 2-param read tool with nested objects, this is nearly everything an agent needs to invoke it correctly.

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 description coverage is 100%, so both parameters are already documented. The description's note about passing a partial `context` largely restates the schema's own wording ('Optional partial context, inlined as the `context` arg...'), adding little new meaning. 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 states a precise verb+resource ('Fetch the underlying LOGIC of flags') and clarifies the non-reducing behavior with a concrete GraphQL shape (`query { root { <selection> } }`). It implicitly distinguishes itself from value-resolution via 'rather than a single resolved value', but never names the sibling (hypertune_evaluate) that embodies the contrast.

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?

'useful for inspecting how a flag is configured' gives a usage context, and the non-reduced framing implies an alternative exists. However, no sibling is named and no explicit when-not condition is given, so selection versus evaluate/introspect remains inferential.

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