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

Annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false) already establish a safe read operation. The description adds valuable behavioral context: requires an API token via _apiKey, returns matching records plus a meta count, and shows a concrete invocation example. No contradiction with 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 three sentences: purpose, return behavior, and requirement, followed by a compact example. It is front-loaded with the core search capability and contains no filler; every sentence earns its place.

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 moderately complex search tool with no output schema, the description conveys the return shape (records plus meta count), the auth requirement, and pagination. Advanced searchCriteria behavior is left to the schema, but the core usage context is complete. A small gap is the absence of guidance on when to use query vs searchCriteria, though the schema hints at it.

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 100%, so the schema already fully documents all five parameters. The description repeats the example values for query/take/_apiKey but adds no new semantic meaning beyond what the schema provides, so baseline 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 verb ('Search'), a specific resource ('BatchData's 155M+ property database'), and the mechanism (location and attribute filters with skip/take pagination). It clearly distinguishes itself from siblings like batchdata_property_lookup by framing this as a broader search returning records plus a meta count.

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?

No explicit when-to-use or when-not-to-use guidance is provided. The description implies this tool is for property searches but does not route the agent away from siblings like batchdata_property_lookup or batchdata_skip_trace, so the agent must infer selection from tool names alone.

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