Truecaller Data2 MCP Server

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Truecaller Search' implies a lookup operation that might involve external services, but it doesn't disclose any behavioral traits like rate limits, authentication requirements, privacy implications, or what happens with invalid inputs. The description is too minimal to provide meaningful transparency beyond the basic action implied by 'Search'.

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 extremely concise with just two words, 'Truecaller Search'. It's front-loaded and wastes no space, though this conciseness comes at the cost of clarity. Every word earns its place by at least hinting at the tool's domain (Truecaller) and action (Search).

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 no annotations, no output schema, and a simple input schema with one parameter, the description is incomplete. It doesn't explain what the tool does beyond the vague 'Search', what results to expect, or any behavioral context. For a tool that likely interacts with an external service (Truecaller), more information about its purpose and output would be needed for adequate completeness.

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%, with the parameter 'number' documented as requiring a string like '919999999999'. The description adds no additional meaning about parameters beyond what the schema provides. According to the rules, with high schema coverage (>80%), the baseline score is 3 when no param info is in the description, which applies here.

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 'Truecaller Search' restates the tool name 'search' with a brand modifier, making it essentially tautological. It doesn't specify what resource is being searched (phone numbers? contacts? databases?) or what action is performed (lookup? verify? identify?). While 'Search' implies a lookup operation, the lack of specificity about what is being searched and what results are returned makes this vague.

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 is provided about when to use this tool. There are no sibling tools mentioned, so no alternative comparisons are needed, but the description doesn't indicate any context, prerequisites, or constraints for usage. The agent must infer usage from the parameter name 'number' alone, which is insufficient guidance.

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