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

No annotations are provided, so the description carries the full burden. It implies a read by using 'lookup', but discloses nothing about permissions, rate limits, failure behavior for unknown parcel IDs, or what the result contains.

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 front-loaded sentence with zero filler and no redundancy. It is efficient, though the brevity comes partly from under-specification rather than tight editing.

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 two-parameter lookup with no annotations and no output schema, the description should at least describe return shape and identifier formats. It says nothing about results, errors, or whether matches are unique, leaving the agent unable to predict the outcome.

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 0%, so the description is the only source of parameter meaning. It usefully identifies both required parameters and frames them as the composite exact-match key, but adds no expected format (e.g., state abbreviation vs full name, parcel_id syntax), which is a real gap for an exact lookup.

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?

States a specific verb (lookup) and resource (parcel) plus the keys used, so the core action is unambiguous. However, it does not distinguish itself from nearby siblings like estate_search, estate_owner, or estate_property_audit, which also concern parcels.

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 word 'Exact' weakly implies that fuzzy/partial matching belongs to estate_search, but that alternative is never named and no when-to-use or when-not-to-use condition is given. The agent must infer routing from a single adjective.

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