SmartProspect: list seniority levels

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

Annotations already declare readOnlyHint and destructiveHint, and the description adds concrete details: 'does not consume credits,' 'creates or modifies remote state: no,' 'can send email: no,' and the endpoint URL. This goes beyond annotation basics, clarifying credit usage and remote effects.

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, with the main purpose in the first sentence, followed by a structured safety summary and endpoint. Every sentence provides distinct value, and the formatting is clean and scannable.

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-list tool with an output schema, the description covers purpose, safety profile, endpoint, and credit consumption. It does not need to explain return values because the output schema exists, and the low complexity means no missing behavioral constraints.

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 parameters (limit, offset, search) are fully documented in the schema. The description adds no further semantic detail about how these parameters affect the list, 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 states 'List seniority level values available as SmartProspect search filters,' which clearly identifies the verb (list), resource (seniority levels), and scope (search filters). This distinguishes it from sibling list tools like list_countries or list_departments.

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: 'Reference data only. Does not reveal contacts and does not consume credits.' This implies it is for retrieving filter values, not contact data. It does not explicitly name alternatives or exclusions, but the context is clear enough for an agent to decide when to use it.

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