Find company accounts in Freshsales CRM by name, domain, or keyword to locate the record you need before viewing or updating it.
Search accounts (companies) by name/domain/keyword.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search term |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It doesn't disclose behavioral traits such as pagination, result limits, fuzzy vs exact matching, or whether it searches only account names or also associated fields. For a search tool, this is a significant gap.
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?
A single, efficient sentence that is front-loaded with the core action. No wasted words.
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?
For a search tool with no annotations and no output schema, the description is incomplete. It doesn't explain return format, result limits, or how to use the results. The sibling list includes list_accounts and view_account, but the description doesn't help an agent choose between them.
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 coverage is 100%, so the single parameter 'query' is already documented. The description adds minor value by specifying that the query searches name/domain/keyword, but doesn't elaborate on syntax or matching behavior.
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?
States a specific verb (search) and resource (accounts/companies), and clarifies what fields are searchable (name/domain/keyword). It distinguishes from list_accounts and view_account by being a search operation, though it doesn't explicitly differentiate from search_leads/search_contacts.
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?
No guidance on when to use this tool versus alternatives like list_accounts or view_account. The description implies a search context but doesn't state exclusions or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.