Check whether a user has a linked Gmail account. Use the user ID to verify Gmail account linkage before sending email or accessing Gmail data.
Return whether the user has a linked Gmail account
| Name | Required | Description | Default |
|---|---|---|---|
| user_id | No |
| Name | Required | Description | Default |
|---|---|---|---|
| No | |||
| scopes | No | ||
| connected | Yes | ||
| granted_at | No |
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description must disclose behavior. It only states the return type but does not mention network activity, auth requirements, error conditions, or side effects.
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 sentence is concise, but could benefit from front-loading key information. 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?
Given no annotations and one undocumented parameter, the description is too minimal. It does not clarify the role of user_id, prerequisites, or what the output looks like despite having an output schema.
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 0% and the description does not mention the single optional parameter 'user_id'. It adds no meaning beyond the schema.
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 clearly states the tool returns a boolean about linked Gmail account, using specific verb 'Return' and resource 'whether the user has a linked Gmail account'. It distinguishes from sibling tools that perform actions or retrieve detailed data.
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 on when to use this tool vs alternatives, such as checking before using other gmail tools. Lacks any usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.