search_tax_foreclosures

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fully discloses matching semantics (case-insensitive substring for nhood, exact for zip/status), the limiting behavior via 'limit', and a known data-quality issue (status nulls) with reassurance that it's not a client bug. This is exemplary transparency.

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 well-structured: a one-sentence purpose, brief operational notes, a caveat, a concise Args list, and a Returns line. Every sentence adds value; there is no fluff or redundancy.

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?

Given the tool's complexity (4 optional filter params, no output schema, no annotations), the description is complete: it explains matching semantics, default behavior, data caveats, and return value shape. An agent has enough to invoke it correctly and interpret results.

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 schema provides zero description coverage, but the description includes an Args section that defines each parameter with type examples, default behavior, and matching rules. This fully compensates for the schema's lack of semantic information.

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 opens with 'Search active Mecklenburg County tax foreclosures,' using a specific verb and resource, clearly indicating the tool's purpose. The scope ('active', county-specific) distinguishes it from sibling parcel/lookup tools like lookup_parcel.

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?

It states that all filters are optional and combined with AND, and explains the default behavior when omitting all filters. It also provides a concrete note about the status field data gap and its impact on filtering, though it does not explicitly name alternative tools or when to choose them.

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