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

No annotations are supplied, so the description carries the full disclosure burden, yet it says nothing about read-only nature, permissions, pagination behavior (despite a per_page cap of 25), or result shape. For a data-retrieval tool with zero annotation coverage, this leaves the agent uninformed about basic behavior.

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 short fragment with no wasted words and the scoping keys are front-loaded, but the brevity comes from under-specification rather than discipline. A tool with three parameters and no annotations needs more than one noun phrase.

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 annotations, no output schema, 0% parameter coverage, and a 25-item page cap, the description is too thin to let an agent call the tool confidently. It omits return format, pagination, and how results relate to sibling tools such as estate_search or estate_coverage.

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 0%, so the description must compensate. It clarifies that 'name' means owner name and that 'state' scopes the lookup, which adds real value, but the third parameter (per_page, max 25) is left entirely undocumented in both the description and 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 fragment identifies a specific resource ('an owner's parcel portfolio') and its two lookup keys ('by state and owner name'), so an agent can roughly infer it returns parcels for an owner. However, there is no verb (retrieve/list/lookup) and nothing distinguishing it from siblings like estate_search, estate_parcel, or estate_coverage, which plausibly overlap on the same parcel data.

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 description gives no when-to-use guidance, no conditions or prerequisites, and never mentions the closely related siblings (estate_search, estate_parcel). The agent must guess whether this is the right tool for an owner lookup versus a general parcel search.

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