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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the description adds value by detailing what is NOT performed (no fee quote, no payment inspection, no charge, no packet generation, no submission) and by noting sandbox checkout requires separate authenticated tools. It doesn't cover rate limits or how evidence requirements are formatted, but it meaningfully extends the annotations.

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?

Three dense, front-loaded sentences: purpose first, then the negative scope list, then the sandbox pointer. No filler, though the phrase 'service capabilities' is a bit abstract for a research 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?

There is no output schema, so the description's note that it returns 'source observations and service capabilities' carries return-value information, and the negatives define the boundary well. It could say more about evidence-requirement structure, but for a research-style tool with fully documented params this is largely complete.

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 four parameters are already documented, including the county adapter key and the enumerated service types. The description only restates the framing ('explicitly selected property', 'requested service') without adding syntax or validation nuance 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 states a specific action and scope: research an explicitly selected property and identify evidence requirements for a requested property-record service. It distinguishes this from the sandbox checkout path (start_tax_sandbox/complete_tax_sandbox_order) by naming that alternative, though the boundary with get_microtransactions_catalog remains implicit.

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 clearly frames usage: research an already-selected property, not a discovery step, and it names the exclusions (no savings, no fee quoting, no charging, no filing, no correction) plus the alternative route for checkout. It stops short of saying which of the many sibling audit_* tools to prefer, but the context is clear and the exclusions are useful.

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