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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds meaningful context beyond this by noting the BatchData API token requirement and by clarifying that it supports one or more known addresses. There is no contradiction with 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?

The description is two concise sentences with a runnable example. The first sentence front-loads the action, scope, and returned data categories, while the example shows the exact call shape. There is no filler or redundancy.

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?

Together with the fully described schemahare, the description covers the tool's purpose, authentication requirement, single-vs-batch input shapes via the requests field, and the categories of returned data. No output schema is needed because the description enumerates the relevant attribute groups. This is sufficient for an agent to invoke the tool correctly.

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?

The input schema already provides 100% description coverage for all parameters, including _apiKey, address fields, and the optional requests array. The description's example mirrors the schema's own example and does not add semantic meaning beyond what the schema already documents, so the baseline of 3 is appropriate.

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 ('look up') and resource ('full property attributes' including owner, building characteristics, valuation, sale/tax history) for one or more known addresses. It is clear and functional, but it does not explicitly differentiate itself from siblings like batchdata_property_search or batchdata_skip_trace, so it stops short of a 5.

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 clearly establishes the intended use case: retrieving complete property attributes when addresses are already known. It does not explicitly name alternatives or state when not to use the tool, though the 'known addresses' phrasing provides useful contextual guidance for choosing this over a search-style sibling.

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