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

With no annotations, the description carries the full burden of behavioral disclosure. It provides none: no indication of whether this is a read operation, what output or side effects occur, what 'compared comparison' means, or what the tool actually does when invoked. The description adds no behavioral transparency beyond the name.

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 short but not well-structured: 'compared comparison' is redundant and confusing. The intended meaning is not front-loaded, and the awkward phrasing weakens what little clarity exists.

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?

The tool has no output schema and no annotations, and the description leaves critical information undefined: what 'Six routes to a completed conveyance' refers to, what kind of comparison is performed, what the result looks like, and how this differs from the sibling compare tools. An agent cannot confidently select or invoke this tool based on the provided definition.

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 tool has zero parameters and schema description coverage is 100%, so there is no parameter documentation burden. The description references 'criteria and any filters' as conceptual content, but since no input schema exists, no parameter explanation is required.

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 tautology of the tool name: compare_criteria is described as 'criteria ... compared comparison.' It identifies the subject matter (criteria and filters of the Six routes to a completed conveyance), but fails to state a clear action such as 'compare', 'view', or 'return' and does not distinguish what this tool does versus the sibling tools compare_options or compare_table.

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 compare_criteria versus compare_options, compare_table, or the enquiry_* siblings. No context, conditions, or exclusions are provided, so an agent cannot determine the appropriate selection among the listed siblings.

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