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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds real context beyond that: a hard geographic scope limited to Chattanooga, Nashville, Memphis, and Knoxville, and the fact that output can be framed as Exhibit P under cited Tennessee statute. It stops short of describing data recency or behavior when permit records are absent.

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 that leads with the verb and resource before piling on statute citations and parentheticals. Dense, but every clause contributes scope or output detail rather than restating the name.

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?

With no output schema, the description does well to name the three categories of findings and the Exhibit P output option. It leaves open how results look when records are missing, whether non-Tennessee parcels are rejected, and how county/jurisdiction inputs interact, which matters for a six-parameter audit tool.

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 100%, so all six parameters are already documented, and the description adds only marginal meaning beyond that by tying 'Exhibit P' to the statutory framing and confirming the four target jurisdictions. Baseline 3 is appropriate since the schema carries the parameter burden.

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 names a specific verb (audit) and resource (municipal building, renovation, and demolition permit records) and enumerates the exact findings produced: premature lien-date additions, demolished structures still on CAMA rolls, and maintenance protections under T.C.A. § 67-5-601/603. That level of specificity clearly separates it from siblings like audit_parcel_blight_citations or audit_property_tax.

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?

Usage is implied by the audit framing and the listed jurisdictions, so an agent can infer this is the permit-history audit for a parcel. However, there is no explicit when-to-use versus alternatives, no prerequisites, and no statement of what to do when a property sits outside the four named cities.

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