SmartProspect: list job titles

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description goes further by stating 'may consume SmartProspect credits: no', 'creates or modifies remote state: no', 'can send email: no', and 'does not reveal contacts'. This adds valuable context beyond annotations and includes the endpoint for clarity.

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: a one-sentence purpose, a structured safety block, and an endpoint. Every sentence provides useful information without redundancy.

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 list tool with an output schema, the description covers purpose, safety, endpoint, and explicitly clarifies that it does not expose contacts or consume credits. This is complete for the tool's complexity.

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 description coverage is 100%, so the schema fully documents limit, offset, and search. The description adds no additional parameter semantics beyond the schema, so the baseline score of 3 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 starts with 'List job title values available as SmartProspect search filters' – a specific verb and resource that clearly distinguishes this from sibling list_* tools (countries, states, cities, etc.). It also notes 'Reference data only. Does not reveal contacts', differentiating it from contact-related tools.

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 provides clear context: this returns reference data for SmartProspect search filters and explicitly states it does not reveal contacts or consume credits. This implies when to use it (needing filter values) and when not (needing contacts), though it doesn't name alternative tools explicitly.

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