owner.pierce

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

Describes veil-piercing capability and data sources (SEC, sponsor rollup, county filings). Mentions return structure and confidence levels. No annotations provided, so description carries full burden. Could mention idempotence/side effects, but implied read-only.

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?

Well-structured with front-loaded purpose and actionable guidance. Each sentence adds value; slightly long but not excessive.

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?

Covers return structure, confidence tiers, and example use cases. No output schema, so description compensates well. Lacks error handling info but overall sufficient for the complexity.

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?

Adds context beyond schema: name normalization, state filter optional, ticker resolution logic. Schema descriptions are already good; tool description enriches understanding.

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?

Clearly states the tool resolves an owner name/entity to its full property portfolio. Distinguishes from sibling parcel.lookup by explicitly saying when not to use it.

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?

Explicitly says when to use (user names an owner) and when not to use (starting from a parcel, use parcel.lookup). Also describes ticker behavior and best-effort resolution.

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