search_crm

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

No annotations are provided, so the description must carry the full burden. It discloses that results include linked records (e.g., timeline event with associated contact and listing) and that it is a single call. However, it does not mention whether the operation is read-only, any rate limits, or pagination behavior.

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 paragraph. It front-loads the core functionality in the first sentence and then provides concrete examples. No unnecessary information.

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 complexity of 8 parameters and no output schema, the description covers the purpose, cross-record linking, and typical use cases. It lacks information about output format or limits, but the examples and parameter context provide sufficient guidance for an AI agent.

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 with descriptions for all 8 parameters. The description adds meaning beyond the schema by explaining how parameters combine (e.g., dateFrom/dateTo with keyword) and providing usage context (e.g., 'query is optional if filtering by date/type').

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 explicitly states that the tool searches across the entire CRM (contacts, listings, tasks, notes, timeline events) in one call, linking results. This clearly differentiates it from sibling tools that operate on single record types (e.g., get_contact, find_listings).

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 provides concrete use cases ('who did I meet at the open house last weekend', 'what listings does this client have') and implicitly guides away from this tool for dedicated listing date queries by referencing the 'listingDateField' parameter and suggesting 'prefer find_listings'. However, it does not explicitly list when not to use it.

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