SmartProspect: list companies

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

An enumeration of safety properties is provided: read-only, no credit consumption, no state modification, no email sending, no destructive behavior. It also adds the exact endpoint and clarifies that it does not reveal contacts, going well beyond the annotation hints and giving the agent confidence in side-effect-free use.

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 and front-loaded with the purpose. Every line adds value: purpose, safety details, endpoint, and reference-data clarification. No wasted words.

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?

This is a low-complexity list operation with a high-quality schema, an output schema present, and clear safety/endpoint disclosure. The description sufficiently covers what the tool does, its constraints, and its non-contacting scope, making it complete for agent decision-making.

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 documents all three parameters with complete descriptions (100% coverage). The tool description adds no extra information about limit, offset, or search semantics, so it earns the baseline score for schema-covered parameters.

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 clear verb+resource statement: 'List company names available as SmartProspect search filters.' It also distinguishes from sibling contact-search tools by noting 'Does not reveal contacts,' making its scope unambiguous.

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 implies the use case (retrieving reference data for filter options) and explicitly states 'Reference data only,' which excludes contact discovery. However, it does not name specific alternative tools or when-not-to-use conditions, so it stops short of full explicit guidance.

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