SmartProspect: list states

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

The description goes beyond annotations by explicitly stating no credits are consumed, no remote state is modified, no email is sent, and no contacts are revealed. It also provides the exact endpoint. These details enrich the annotation-provided readOnlyHint=true and destructiveHint=false without contradiction.

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 well-organized: one-sentence purpose, a structured safety profile, endpoint, and a reference-data caveat. Each sentence earns its place, though the safety list is somewhat redundant with annotations, keeping it from a perfect 5.

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 simple read-only list tool. The description covers purpose, safety, endpoint, and the nature of the data, while the input schema fully documents parameters and an output schema exists. No significant gaps remain for an agent using 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?

Input schema has 100% parameter description coverage, so the baseline is 3. The description does not add additional parameter-specific semantics beyond noting the tool provides filter values; it neither clarifies formats nor adds usage constraints beyond what the schema already documents.

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 state/region values available as SmartProspect search filters,' specifying a specific verb and resource. This distinguishes it from sibling list tools like list_countries or list_cities by naming the exact type of value (state/region) and its purpose (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 description implies the tool is for retrieving reference data to use in SmartProspect search filters and explicitly notes it does not reveal contacts. It provides clear context, but does not explicitly name alternative tools or state when not to use it, so it falls short of a perfect 5.

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