parcel.search

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

Adds context beyond schema: backend index, query types, default/max limits, and summary fields. Lacks explicit read-only statement but no annotations to contradict.

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?

Four sentences with purpose first, then return structure, usage guidance, and backend context. No redundant words.

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?

Covers core use cases, filtering, pagination, and sibling differentiation. Lacks detail on error handling and exact ranking logic, but sufficient given no output schema.

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?

With 50% schema coverage, the description clarifies `q` usage and limit defaults but does not detail other parameters like `sort`, `dir`, or `page` beyond schema constraints.

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 clearly states 'Filter US parcels by geography + attributes' and differentiates from siblings with explicit 'Do NOT use' instructions for parcel.lookup and parcel.compare.

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?

Provides concrete use cases ('absentee-owned SFR in Mecklenburg County...') and explicit when-not-to-use scenarios, giving the agent clear decision criteria.

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