SmartProspect: list countries

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

Beyond the annotations (readOnlyHint, destructiveHint, openWorldHint), the description explicitly enumerates safety properties: no credit consumption, no remote state changes, no email, no destructive actions. It also provides the exact endpoint and clarifies that the tool returns reference data only, which exceeds annotation coverage.

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 three sentences: the first clearly states the purpose, the second provides a structured safety summary, and the third reinforces the reference-only nature. Every sentence adds distinct value without repetition or fluff.

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 an output schema present, the description covers purpose, safety, endpoint, and usage context. It fully addresses the tool's function and constraints, making it complete for an AI agent to decide when and how to invoke it.

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 detailed descriptions for limit, offset, and search. The description adds no additional parameter-specific meaning; it only frames them as search filters. Baseline 3 is appropriate since the schema carries the explanatory burden.

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 starts with 'List country values available as SmartProspect search filters,' which is a specific verb+resource statement. It clearly identifies the tool as a reference data listing for countries and distinguishes it from sibling list tools (states, cities, industries, etc.).

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 states the tool lists country values for use as search filters, implying when to use it. It adds 'Reference data only' and 'Does not reveal contacts,' which clarifies it is not for lead retrieval. However, it does not explicitly name alternative tools or state when not to use it, so it misses the top score.

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