SmartProspect: list company domains

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

Beyond annotations, the description details specific safety traits: 'read-only: yes; may consume SmartProspect credits: no; creates or modifies remote state: no; can send email: no; destructive: no.' It also states 'Does not reveal contacts' and includes the endpoint, adding valuable behavioral context. No contradictions 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 concise and front-loaded with the primary purpose. The safety and endpoint details are provided in compact, structured lines. The slight repetition of 'does not consume credits' is minor and does not detract from overall clarity.

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?

The tool is simple, has an output schema, and the description covers purpose, safety, endpoint, and reference-data nature. It does not need to explain return values given the output schema. The description is sufficiently complete for an AI agent to select and invoke this tool correctly.

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 has 100% description coverage, so all three parameters (limit, offset, search) are already documented with defaults and ranges. The tool description adds no additional parameter semantics beyond what the schema provides, aligning with the baseline of 3.

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 'List company domains available as SmartProspect search filters,' which is a specific verb+resource statement. It clearly distinguishes from sibling list tools by targeting company domains, not countries, states, or other filter types. The title reinforces this.

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 statement 'available as SmartProspect search filters' provides clear context for when to use the tool: to obtain domain options for building search filters. 'Reference data only' adds context that this is not for contact retrieval. However, it does not explicitly name alternatives or state when not to use it, stopping 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.