SmartProspect: list departments

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

Beyond the annotations (readOnlyHint, destructiveHint), the description explicitly discloses that it consumes no SmartProspect credits, sends no email, creates/modifies no remote state, and does not reveal contacts. This provides concrete safety and side-effect context that annotations alone don't cover, with no contradictions.

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 and front-loaded, leading with the core purpose, followed by safety assertions, endpoint, and a concise note about reference data. Every sentence adds useful information with no 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?

Given the low complexity of a reference-data list tool, the description fully covers what an agent needs: purpose, safety profile, endpoint, and the fact that it neither reveals contacts nor consumes credits. The output schema is present, so return-value details are handled externally.

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 covers all three parameters (limit, offset, search) with detailed descriptions, so schema coverage is 100%. The description adds no additional parameter-specific semantics, so baseline 3 is appropriate per the rubric.

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 a specific action and resource: 'List department values available as SmartProspect search filters.' This clearly distinguishes it from sibling reference-data tools like list_countries or list_industries. The endpoint is also provided for additional clarity.

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 usage context by stating these are 'search filters' and 'Reference data only,' making it clear this is for retrieving filter options. However, it doesn't explicitly mention when to prefer this tool over other list_* tools or search_contacts, though the name and purpose make this fairly evident.

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