Filter Leads

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

No annotations are provided, so the description must disclose side effects and safety. It states the filtering operation but does not say whether the tool is read-only, how results are returned, or any pagination/limit behavior. The phrase 'Filter stored leads' implies a non-mutating query, but this is not explicit.

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 a single, front-loaded sentence with no filler. It efficiently names the action and key filtering dimensions.

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?

The description captures the core filters but omits important context: the limit parameter, whether all filters are optional, and how filters interact. An output schema exists, so return values don't need description, but for an 11-parameter tool, the description is minimally viable rather than fully complete.

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?

With 0% schema description coverage, the description adds meaning by grouping parameters into three categories: keyword, required field presence (has* flags), and minimum confidence (minConfidence). However, it does not explain the limit parameter or how the filters combine (AND/OR), so it only partially compensates for the schema's lack of descriptions.

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 uses the specific verb 'Filter' and identifies the resource as 'stored leads,' with explicit criteria (keyword, required field presence, minimum confidence). This clearly distinguishes it from siblings like list_stored_leads, which lists leads, and search_web, which is web search.

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 (filtering stored leads) but provides no explicit guidance on when to use this vs alternatives like list_stored_leads, nor any exclusions or prerequisites. There is no 'use this when...' language, so usage is only implied.

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