google_contacts_listList contacts from a specified Google account, returning names, emails, and phone numbers. Use pageSize to limit results.
List the account's contacts with names, emails and phones.
| Name | Required | Description | Default |
|---|---|---|---|
| account | No | Account nickname to use. | |
| pageSize | No | Max contacts (default 100). |
Changes observed during successful MCP inspections.
v0.1.30Input schema / additionalPropertiesRemoved value: -falsev0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It states that contacts are listed with names, emails, and phones, providing partial output context, but does not mention whether the operation is read-only, pagination behavior, or authentication requirements. This is a significant gap for a tool without annotations.
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 a single, front-loaded sentence that is concise and to the point, with no extraneous information. It efficiently conveys the core purpose and key output fields.
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 simplicity of the tool and the absence of an output schema, the description provides the essential field names but omits details like pagination behavior, error handling, and whether all contacts are returned without filtering. While adequate for a basic listing, it could be more complete to fully inform the agent.
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?
Both parameters (account and pageSize) are fully described in the schema, so the description does not need to add details. It adds no extra meaning beyond the schema, which matches the baseline of 3 for high schema coverage.
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 action (list) and resource (the account's contacts), specifying the returned fields (names, emails, phones). This distinguishes it from siblings like google_contacts_search and google_contacts_create, though it does not explicitly name them. The verb and resource make the purpose unambiguous.
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 given on when to use this tool versus alternatives like google_contacts_search. The description does not mention when to list all contacts versus searching for specific ones, nor any prerequisites. This leaves the agent to infer usage without explicit direction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.