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

No annotations are provided, so the description must carry the behavioral burden. It discloses the external SSURGO dependency and that the tool detects misclassifications and calculates overcharges, but it does not explicitly state read-only status, permission requirements, failure modes, or whether any records are modified.

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 front-loaded sentence with no wasted clauses, and the core action is clear immediately. It is slightly dense due to the statutory citation and Exhibit G reference, but each clause contributes domain specificity.

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?

There is no output schema and no annotations, so the description should explain what the audit returns, how Exhibit G output is produced, and key limitations or prerequisites. It identifies the domain purpose but leaves an agent without enough behavioral and output context to call it confidently beyond the parameter 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?

Schema description coverage is 100%, so all seven parameters are already documented in the schema. The description does not add format, constraints, or usage notes beyond naming the audited parcel, so the baseline of 3 is appropriate.

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 states a specific verb and resource: auditing a parcel against USDA NRCS SSURGO soil data for Greenbelt misclassification, soil capability classes, and statutory overcharges. This clearly differentiates it from tax-focused or topography-focused siblings such as audit_property_tax and audit_parcel_topography.

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 implies the use case: a parcel with possible Greenbelt agricultural productivity misclassification and present-use overcharge exposure. However, it does not explicitly say when to use this rather than siblings like check_eligibility, audit_property_tax, or audit_parcel_topography, nor does it state prerequisites such as Greenbelt enrollment.

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