SmartProspect: list revenue ranges

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

Beyond the annotations, the description reveals that the tool does not reveal contacts, does not consume SmartProspect credits, and takes no pagination parameters (meaning returns all data at once). It also provides the endpoint URL, adding useful behavioral context.

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 concise and front-loaded: the first sentence states the purpose, followed by safety, endpoint, reference nature, and pagination. Each sentence earns its place with no redundant information.

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 zero-parameter reference-data list tool, the description covers purpose, safety, credit consumption, contact privacy, and pagination. An output schema exists, so detailed return format is not needed in the description.

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 tool takes zero parameters, and the input schema confirms this. The description adds that the endpoint takes no pagination parameters, which aligns with the schema. Per baseline for 0 params, a score of 4 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 clearly states 'List company revenue range values available as SmartProspect search filters' with a specific verb and resource. It distinguishes from sibling list tools by specifying the exact data type (revenue ranges) and their role as search filters.

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 to use this tool (when needing reference values for filters). However, it does not explicitly name alternatives or mention when not to use it, so it stops short of a 5.

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