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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond them: the call is free with nothing charged, results show price and lead count, and skip tracing does not change the price — all facts an agent cannot derive from 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?

Front-loaded with what the tool returns and how to scope it, then pricing facts and the hand-off to get_package_quote. Every sentence carries information, though the skip-tracing price remark is the least essential line.

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 read-only listing tool with no output schema, the description covers the essential call shape (state + county), result contents (price, lead count), cost (free), and next step (get_package_quote). The only meaningful gap is guidance on the limit parameter and pagination behavior.

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 coverage is 50%, so the schema already documents state and county with examples. The description reinforces the one-county-at-a-time constraint and names the Probate/FirstUp lead types that map to the lead_type enum, but it says nothing about the limit parameter or its 1-100 range and default of 25.

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?

States a specific verb and resource ('List LeadFuzion lead packages for sale'), names the two catalog types (Historical Probate, FirstUp), and pins the unit of listing to one county and one month. It also routes the agent to get_package_quote for terms, so it is distinguishable from at least one sibling without opening a schema.

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?

Gives clear operating context: pass state and county because the catalog is listed one county at a time, and call get_package_quote for terms and payment. There is no explicit exclusion such as when to use buy_package instead, so it stops short of full when/when-not guidance.

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