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

With no annotations, the description carries the full load: it does disclose that this is a mutation with real consequences (enforce, strip penalties, issue injunction), which is valuable. It says nothing about required documentation, authorization, whether enforcement is actual or simulated, or how the injunction is served, leaving significant gaps for a write operation.

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?

A single dense sentence with zero filler, front-loading the statutory basis and the enforcement outcome. Every clause maps to a distinct capability of the tool.

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 an 11-parameter mutation tool with no annotations and no output schema, one sentence is thin: it omits what the audit returns, what enforcement artifacts are produced, and the relationship between the two required fields (servicemember_name, active_duty_start_date) and the computations. Adequate but with clear gaps.

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 11 parameters with examples (e.g. interest rate as 0.18, date formats). The description adds one piece of semantics the schema does not: the 6% statutory cap that contextualizes county_interest_rate_annual and the penalty stripping that relates to billed_accrued_interest_and_penalties.

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?

Names a specific verb pair (audit and enforce) and a precisely scoped resource: the SCRA 6% delinquent property tax interest cap, cited to statute. The added actions (strip penalties, issue stay of tax sale injunction) make it distinguishable from siblings like audit_property_tax or audit_combat_deployment_abatement.

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 statute and the 'delinquent property tax' framing imply when the tool applies, but there is no explicit routing guidance versus audit_property_tax, check_delinquent_taxes, or the other veteran-relief auditors. An agent must infer selection from the mention of servicemember status and a county interest rate.

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