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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not say what the tool does, what it returns, whether it is a read-only lookup, or how the criteria and filters are presented. The description only names the subject matter.

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 very short and free of filler, but it is structured as a fragment rather than a complete instruction. Missing a verb makes it less useful, and the brevity crosses from concise into under-specified.

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 tool with no output schema and no annotations, the description should state what the caller receives or can expect. 'The criteria and any filters' hints at content but does not explain the return value, format, or behavior, leaving the tool incomplete for an agent to call confidently.

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 has zero properties, so there are no parameters whose semantics need clarification. The description does not need to compensate for missing parameter documentation, and the baseline for a zero-parameter tool 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 is essentially a noun phrase that restates the tool's name and title: it says the tool is about 'the criteria' of a comparison, which is what 'compare_criteria' and 'What is compared' already say. It adds domain context ('US HVAC field service software') but no explicit verb or action, so an agent cannot tell whether the tool returns criteria, explains them, or accepts them as input.

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?

There is no guidance on when to use this tool versus the siblings such as compare_options, compare_table, or enquiry_fields. The description does not state a condition, context, or exclusion that would help an agent choose this tool instead of an alternative.

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