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

Beyond the readOnlyHint annotation, the description discloses that the result is an estimate with bounds and an is_estimated flag, and that it matches the Interactive Methodology Explorer. This adds meaningful behavioral context about uncertainty and output interpretation. It does not over-explain side effects, but for a read-only estimation tool this is adequate.

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 three concise, front-loaded sentences. The first sentence states the primary action, the second names the return structure and methodology link, and the third gives a critical usage caution. Every sentence earns its place with no redundancy or filler.

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?

With no output schema, the description compensates by stating the return format (point estimate + bounds) and the is_estimated flag. It also references the methodology URL for deeper context. It could mention units or clarify how the precision parameter interacts with 'BF16,' but overall it provides enough context for an agent to invoke the tool and interpret results.

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?

The input schema already documents 4 of 5 parameters with descriptions (80% coverage), so the baseline is 3. The tool description itself does not add detailed parameter-level semantics beyond noting 'BF16' and 'hardware configuration,' which maps loosely to the precision and hardware_type/unit_count parameters. This is sufficient but not exceptional.

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 opens with a specific verb and resource: 'Compute peak BF16 FLOP estimates for a hardware configuration.' This clearly distinguishes the tool from its siblings, which all concern entity lookups or searches. It also immediately conveys the tool's core purpose and precision focus.

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 clear usage context by stating the tool returns a point estimate plus bounds and points to a methodology reference. It also gives an explicit 'do not' instruction: 'Do NOT present outputs as exact measurements — always relay the bounds and the is_estimated flag.' It does not name alternative tools, but the context is sufficient given the sibling set.

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