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

No annotations are provided, so the description carries the full behavioral burden. It does not state that this is a read-only listing, does not describe the return shape, ordering, or whether filtering matches exact/substring tags. The 'optionally filtered' clause is the sole behavioral hint and it is underspecified.

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?

It is a single sentence, but the construction is muddled — "the government charges comparison" reads as a broken clause rather than a front-loaded purpose. Brevity here reflects under-specification and awkward phrasing rather than efficient structure.

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 0% parameter coverage, the description is the only source of information yet leaves the operation ambiguous, the filter mechanism unclear, and the return content unstated. It is inadequate for an agent to invoke this correctly.

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 coverage is 0% and neither parameter name is echoed or explained. The phrase "filtered by a tag value" loosely implies a value match, but the filterKey/filterValue key-value pairing is never clarified, so an agent must guess how the two parameters relate.

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 indicates this returns a set of options (residence routes) with fields like name, best-for, and tags. However, the phrasing "by what the government charges comparison" is garbled and the core verb is buried, making it hard to tell exactly what operation it performs versus siblings compare_criteria and compare_table, which are not differentiated at all.

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 only usage hint is "optionally filtered by a tag value," which gestures at an optional narrowing filter but says nothing about when to choose this over compare_criteria or compare_table, nor any prerequisites. An agent has no routing guidance among the three siblings.

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