get_liens_and_encumbrances

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

No annotations are provided. The description discloses the data sources (DOF, ACRIS) and record types (tax lien sale entries, mortgage documents, lender names, amounts, satisfaction records), adding value beyond the schema. However, it does not cover aspects like pagination, data freshness, rate limits, or required permissions.

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 three sentences long and efficiently conveys purpose, details, and use case without unnecessary words or repetition.

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 tool with 4 parameters, no schema descriptions, and no annotations, the description covers the core functionality and data sources but lacks parameter explanations and mentions of error conditions or rate limits. The presence of an output schema partially compensates, but overall completeness is moderate.

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 description coverage is 0%. The description indirectly links the boolean parameters to tax liens and mortgages but does not explain the 'bbl' or 'limit' parameters, nor does it provide explicit parameter-level guidance. The agent may miss the meaning of 'bbl' as a Borough-Block-Lot identifier.

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 the action (get), the specific resources (tax liens and mortgage/encumbrance records), and details the data sources (DOF and ACRIS) and contents (lender names, amounts, satisfaction records). This distinguishes it from sibling tools like get_tax_info or get_property_history.

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 description provides a use case ('assess a property's debt profile and lien exposure'), suggesting when to use, but does not explicitly state when not to use or compare with alternatives. The implied usage is present but lacks explicit exclusions or comparisons.

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