search_leads_by_term

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

No annotations provided, so description carries full burden. It does not disclose behavioral traits like case sensitivity, search behavior (exact match, fuzzy), or what happens on no results. Lacks authorization or rate limit info. Minimal transparency beyond basic operation.

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?

Description is well-structured, starting with purpose, then usage guideline, then parameter details. Not overly long, but some repetition (defaults stated twice). Every sentence adds value. Could be slightly more concise.

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 output schema exists (not shown), return values are covered. Complexity moderate with 4 params. Description covers parameter meanings and usage context but lacks behavioral details (case sensitivity, pagination behavior beyond defaults). Adequate but not 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?

Schema description coverage is 0%, but the description adds meaning for all 4 parameters: search_term with examples, page as 0-based, size with max, and sort with format example. Provides defaults and constraints. Could mention sortable fields but is still helpful.

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 clearly states 'Search leads by a single term across multiple fields', specifying the verb, resource, and scope. It distinguishes from sibling tool 'search_leads' which filters by specific field, so purpose is distinct and precise.

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?

Explicitly says when to use: when user asks for 'leads with X', 'leads containing Y', 'leads named Z' without field specification. Also explicitly directs to search_leads for specific field filtering. Excellent guidance with a clear alternative.

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