title_chain

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

With no annotations, description fully discloses: powered by ATTOM, costs $0.02 USDC per call, settled on Base mainnet from user's wallet. This covers data source, cost, and payment method. Also indicates it is a read operation (returns data). No contradictions.

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?

Description is 4 sentences, front-loaded with purpose, then usage guidelines, then cost. Efficient but could be slightly more concise. Good structure.

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?

Given single parameter and no output schema, description covers purpose, usage, cost, and data source. It mentions summary and detail but lacks explicit response structure. Still fairly complete for the tool's 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?

Only one parameter (address) with schema description already providing format and example. Coverage is 100% so baseline is 3. The description does not add additional semantics 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 clearly states it returns US property title chain history with specific data types (recorded deeds, mortgages, preforeclosure events) and includes summary and chronological detail. It distinguishes from sibling tools like property_dossier by being specifically about title chain.

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 lists use cases (title verification, ownership history, etc.) and says 'Use this when the user asks about:' providing clear guidance. Does not mention when not to use or alternatives, but the list sufficiently directs usage.

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