SmartProspect: list recent searches

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds safety clarifications beyond annotations: 'may consume SmartProspect credits: no; creates or modifies remote state: no; can send email: no; destructive: no,' plus the endpoint. No contradiction with annotations.

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, front-loaded with the purpose. The safety block and endpoint are useful, but 'read-only' appears twice ('read-only: yes' and 'Free and read-only'), creating slight redundancy. Overall, it is concise and well-structured.

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 read-only list tool with an output schema present and annotations covering safety, the description is complete. It correctly does not need to explain return values or pagination in detail, as the schema already documents limit and offset.

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 100% of parameters (limit and offset) with detailed descriptions including defaults and bounds. The description adds no parameter-specific meaning, but the schema fully documents the parameters, so baseline 3 applies.

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 opens with 'List recently executed SmartProspect searches with their filter details,' which clearly identifies the action and scope. It differentiates from sibling list tools like list_saved_searches and list_fetched_searches by focusing on 'recently executed' searches.

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 does not explicitly specify when to use this tool versus alternatives such as list_saved_searches or list_fetched_searches. The use case of browsing recent search history is implied by 'recently executed,' but no explicit guidance, exclusions, or alternative mentions are provided.

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