SmartProspect: list company head count ranges

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

Annotations already declare readOnlyHint and destructiveHint, but the description adds valuable behavioral context: 'may consume SmartProspect credits: no', 'creates or modifies remote state: no', 'can send email: no', and 'Does not reveal contacts.' This goes beyond the binary hints and clarifies cost and data exposure.

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 compact (about 80 words) and front-loaded with purpose, followed by a structured safety summary and endpoint. Every sentence adds information; the safety bullet duplicates some annotation hints but includes credit and contact exposure details not present in annotations, making it justified.

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 simple reference-data listing tool with a full output schema and 100% parameter coverage, the description provides all necessary context: what it lists, that it's read-only and free, that it does not reveal contacts, and the exact endpoint. No critical gaps.

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 100% with clear descriptions for limit, offset, and search. The description does not add further parameter semantics, so the baseline of 3 applies. It correctly implies these are list-pagination/filter parameters but without additional detail.

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 opens with a specific verb and resource: 'List company head count (size) ranges available as SmartProspect search filters.' This clearly distinguishes it from sibling list tools (countries, industries, etc.) by naming the exact resource (head count ranges) and its role as search filter values.

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 phrase 'available as SmartProspect search filters' provides clear context for when this tool is useful (populating filter options). It does not explicitly exclude alternatives or state when not to use it, but the purpose is self-evident and the description adds 'Reference data only' to set expectations.

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