compare_operator_to_reference

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

The readOnlyHint annotation already signals a safe read operation, and the description adds useful behavioral context by stating it computes from raw metrics and reference field and returns specific comparison components. There is no contradiction with the annotation, and no destructive or side-effect behaviors need disclosure.

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 sentences, with the core purpose front-loaded in the first sentence. Every sentence adds distinct value (purpose, return contents, data source) without redundancy or fluff.

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 a complete input schema and readOnlyHint annotation, the description sufficiently covers purpose and return categories; the presence of an output schema also relieves the need to detail return structures. Minor missing context includes how to select a reference population and potential relationships to sibling comparison tools, but these are not critical for correct invocation.

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%, with operator_id and reference already documented. The description's phrase 'reference field' adds slight ambiguity but essentially restates the reference parameter; it does not provide meaningful additional semantic detail beyond the schema.

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 tool compares an operator to a reference population and lists the return categories (benchmark selection, comparison group, metric comparison). However, it does not explicitly differentiate itself from sibling tools like get_operator_similarity or get_cohort_distribution, which may serve similar comparison purposes.

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 implies usage when an operator-to-reference comparison is needed, and the return types suggest analytical contexts. It offers no explicit when-to-use/when-not-to-use guidance or alternative tool references, leaving the selection inference to the agent.

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