List connected Google accounts and their grant status. To connect a new account, use integrations.connect_google.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | ||
| meta | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the description doesn't need to restate safety. It adds the detail that the list includes 'grant status', which goes beyond annotations and informs the agent about the content.
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?
Two sentences, front-loaded with purpose, and the alternative is given without extra words. Every sentence earns its place.
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 read-only list tool with no parameters, an output schema, and annotations covering safety, this description is complete. It explains what is listed and routes to the sibling for the complementary action.
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?
The tool has zero parameters, so the description adds no parameter detail, and the baseline for zero parameters is 4. The description doesn't mislead or omit anything needed.
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 states a specific verb ('list'), resource ('connected Google accounts'), and the data ('grant status'). It explicitly distinguishes from the sibling integrations.connect_google, so an agent can tell them apart without opening schemas.
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?
The description explicitly says 'To connect a new account, use integrations.connect_google', giving a clear when-not/alternative and implying this tool is for listing existing accounts. Nothing is left to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The tools are largely distinct due to the domain-prefixed naming (inbox, jobs, signals, etc.) and detailed descriptions. While there is some overlap among inbox actions like acknowledge, apply_suggestion, and decline, the descriptions clarify each behavior. The signals and recommendations sub-groups also have clear boundaries, making misselection unlikely.
All tools follow a consistent pattern of domain.entity.action or domain.action (e.g., inbox.list, jobs.interviews.add, signals.recommendations.dismiss). This uniform camelCase-with-dots convention makes the set highly predictable and easy to navigate.
At 55 tools, the server far exceeds the 25-tool threshold for 'too many' as per the calibration. While the broad domain of job search management justifies numerous operations, the count is still overwhelming and could overwhelm agents or cause selection errors. Several signal-related tools could potentially be consolidated without compromising functionality.
The tool set covers the full lifecycle of job applications: inbox management (list, get, draft, send), job tracking (add, update, archive, delete), interviews (add, update, delete), offers (create, update, accept, decline, negotiation), and company signals (track, pause, recommend, block). There are no obvious missing operations for the core workflows.
