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

No annotations are present, so the description carries the full burden of explaining behavior. It states that a comparison is made, but does not disclose whether the tool is read-only, what output format or content to expect, what 'capability comparison' means, or any limitations of the comparison. This leaves the agent with insufficient understanding of the tool's actual behavior.

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 it is poorly structured and contains a redundant tail: 'compared on capability comparison.' It also relies on the unclear title 'What is compared' instead of cleanly stating the tool's action and output. The phrasing is confusing rather than efficiently informative.

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 annotations, no output schema, and no parameters, the description is the only source of context, and it leaves the tool's purpose, output shape, and relationship to sibling tools unclear. An agent cannot reliably know what invoking this tool will do or how to interpret its result.

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?

This tool has zero parameters and an empty input schema, so there are no parameter meanings that the description needs to clarify. The 'criteria and filters' mentioned in the description appear to be the subject of the comparison, not input parameters, so the no-parameter baseline of 4 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 identifies the subject ('criteria and any filters' around 'Who can prepare a UK crypto tax position') and indicates they are 'compared', so it is not merely a tautology. However, the phrasing is vague and awkward ('compared on capability comparison'), and it does not clarify what the tool returns or how it differs from sibling tools like 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?

The description provides no guidance on when to use compare_criteria versus its siblings compare_options, compare_table, enquiry_describe, enquiry_fields, or submit_enquiry. There are no exclusions, alternatives, or conditions given. The phrase 'capability comparison' hints at a use case but is too vague to guide tool selection.

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