global_search

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

No annotations are provided, so the description bears full responsibility. It discloses that results are unified and deduplicated, but does not mention read-only nature, rate limits, authentication requirements, or other behavioral traits. This leaves significant gaps for an agent.

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, well-structured sentence that conveys the core functionality efficiently. There is no redundancy or fluff.

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 tool has 9 parameters (only 1 required) and no output schema, the description should clarify how optional parameters filter results, pagination behavior, and return format. It does not address these, leaving the agent underinformed for proper usage.

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 has 100% coverage, so the baseline is 3. The description adds minimal extra meaning beyond the schema (e.g., mentioning the query parameter implicitly). It does not elaborate on how optional parameters interact or provide examples.

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 of customers across multiple data sources (CRM, contacts, conversations) and returns unified deduplicated results. It distinguishes itself from sibling search tools like search_customers or search_conversations by emphasizing the cross-source scope.

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 use for cross-source customer searches with 'Busca en todas las fuentes de datos de clientes.' It provides clear context but does not explicitly state when not to use it or mention alternative tools for narrower searches.

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