Search Freshsales

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

No annotations are provided, so the description carries the full burden. It only states the operation is a search, implying a read-only action, but does not disclose return format, pagination, search behavior (e.g., fuzzy matching), or any limitations. Without explicit behavioral context, an agent cannot fully anticipate the tool's response or side 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?

Two sentences with no fluff. The first sentence states the core function, the second gives usage context. Every word earns its place, and front-loading is effective.

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 tool is simple with 2 parameters and no output schema, so the description covers the core purpose and usage. However, it omits the return structure and any search semantics (e.g., whether it returns a list, ranking, or partial matches). Given no annotations, the description is somewhat minimal for a search tool.

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 already provides 100% description coverage for both parameters. The description repeats that search can be by name, email, phone, or company, aligning with the query parameter, but adds no new semantic nuance beyond what the schema states. Baseline 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 clearly states the tool performs a global search across Freshsales CRM entities (leads, contacts, deals, accounts) by name, email, phone, or company. It uses a specific verb 'search' and resource 'Freshsales CRM', and the scope distinguishes it from sibling tools like list_records or get_record.

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 explicitly says 'Use this first when the user asks about a specific person or company', which provides clear when-to-use guidance. However, it does not explicitly mention when not to use it or name alternative tools, so it lacks full exclusions.

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