Verify whether a Make.com connection remains valid by re-checking saved credentials with the app, returning a 'verified' status.
Verify whether a Make.com connection is still valid (Make re-checks the saved credentials against the app). Returns a 'verified' status.
| Name | Required | Description | Default |
|---|---|---|---|
| connection_id | Yes | The connection ID (from make_list_connections) |
Changes observed during successful MCP inspections.
v1.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses re-checking credentials and return of 'verified' status. No annotations provided, so description carries burden; it adequately describes the behavior without contradictions.
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?
Single, front-loaded sentence with no unnecessary words. Every part adds meaning.
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?
Simple tool with one param and no output schema; description fully explains purpose, behavior, and return. No gaps.
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?
Single parameter is fully described in schema (100% coverage). Description adds value by hinting at source function (make_list_connections).
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?
Clearly states the tool verifies a Make.com connection's validity using specific verb 'verify' and resource 'connection'. Distinguishes from siblings like make_list_connections which list connections without testing.
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?
Implied usage for checking connection validity before operations, but no explicit when-not-to-use or alternatives. Context from siblings helps differentiate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.