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

With no annotations, the description must carry the behavioral burden. It discloses that the tool audits eligibility, calculates projected 5-year savings, and references base-year locking under the statute, but it does not clarify whether the operation is read-only, what permissions are required, how ineligible cases are handled, or what assumptions drive the savings projection.

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 a single compact sentence that front-loads the primary actions and names the program and statute without wasted text. The statutory citation and base-year reference are dense but directly relevant to the tool's scope.

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 statutory eligibility-and-savings calculation with seven parameters, no output schema, and no annotations, the description is somewhat thin. It names the program and the five-year projection, but it does not explain the output structure, calculation assumptions, or eligibility decision details that would help an agent 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?

Schema description coverage is 100%, so the schema already documents all seven parameters, including the $45,000 income ceiling. The description adds program context such as the five-year projection horizon and base-year lock, but it does not add parameter-specific meaning beyond the schema.

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 uses specific verbs, 'Audit eligibility' and 'calculate projected 5-year savings,' for a clearly named program: the Tennessee Senior Property Tax Freeze. It also cites the governing statute, which distinguishes it from sibling relief tools such as disabled homeowner, disabled veteran, and surviving spouse programs.

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 intended use is implied by the program name and the eligibility-audit framing, but the description does not explicitly state when to use this tool versus siblings like check_eligibility or audit_property_tax. It also does not spell out prerequisites such as age thresholds or the income ceiling, though the income ceiling appears in the schema.

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