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

No annotations are provided, so the description bears the full burden of explaining behavior. It only states criteria and filters as the subject matter and does not disclose whether the tool returns data, lists available options, or performs any other observable action.

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 and places 'criteria' first, but it is an ungrammatical fragment with a long prepositional chain. It could be much clearer with a simple verb-headed sentence such as 'Returns the criteria and filters used for the comparison.'

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 zero-parameter tool with no output schema, the description should clearly state what the call yields. It gestures at criteria and filters, which is probably sufficient for a trivial invocation, but it does not clarify the output format or distinguish this tool from sibling comparison tools.

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, so there is no parameter information for the description to add. The schema already covers everything needed, and the description does not need to compensate for missing parameter docs.

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 resource: criteria and filters in the context of a Field Service Management software comparison. However, it is a noun phrase without an explicit verb like 'lists', 'returns', or 'compares', so the tool's action remains somewhat vague.

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_* sibling tools. No alternatives or conditions are mentioned, leaving tool selection to inference.

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