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

Goes well beyond the readOnly/idempotent annotations, disclosing credit behavior ('never spends credits'), free-tier daily rules, quote-instead-of-rows past free rows, newest-first ordering, and the bbl-to-owner-contacts workflow. This is exactly the kind of cost and side-effect context an agent needs before invoking.

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?

Dense but front-loaded: purpose, alternatives, filters, return shape, then credit rules in a logical progression with zero filler. The credit paragraph is long but earns its length given the quote flow.

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 9-param, credit-gated search tool it covers ordering, page size, paging, return contents (bbl), cost model, and next-step chaining to get_nyc_property/unlock_nyc_owner_contacts. Nothing an agent needs to call it correctly is missing.

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 78%, so the schema documents most params. The description still adds value by mapping the filter list and clarifying that equity only applies to 1-3 family homes; however, it doesn't clarify the amountOwedMin/Max parameters that lack schema descriptions, leaving a small gap.

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?

States a specific verb and resource ('Searches NYC properties in preforeclosure only: lis pendens foreclosure filings') and enumerates the five covered boroughs. It explicitly differentiates itself from find_nyc_property and the national search tools, so an agent can pick it apart from siblings without opening any schema.

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?

Gives explicit routing rules: one property by address → find_nyc_property; filtered or non-NYC → national tools. It also documents the paid-tier flow requiring user confirmation before run_nyc_preforeclosure_search, leaving nothing to inference.

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