Retrieve detailed information for a specific contact by ID from Freshsales CRM. Use it to access contact records and their associated data.
View detailed information about a contact.
| Name | Required | Description | Default |
|---|---|---|---|
| contact_id | Yes | Contact ID |
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 behavioral burden. 'View' implies a safe read operation, which is useful, but it says nothing about permissions, behavior when the contact_id doesn't exist, or what 'detailed information' comprises.
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 front-loaded sentence with zero filler. Every word earns its place and the core action is stated immediately.
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 simple one-parameter read tool with no output schema, the definition is adequate but thin. It doesn't describe the returned fields or error behavior, leaving the agent to infer what 'detailed information' means.
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 100% and the single required param (contact_id) is documented in the schema. The description adds no syntax, format, or ID-source guidance beyond what the schema already provides, so the baseline of 3 applies.
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 ('View') and resource ('contact') with a scope qualifier ('detailed information'). This differentiates it from list_contacts and search_contacts by implying single-record retrieval, though it doesn't name those siblings explicitly.
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?
Usage is only implied: retrieving one contact is clearly distinct from listing or searching, but the description never states when to prefer this over search_contacts or list_contacts, nor any prerequisite such as needing a known contact_id.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.