Create contact

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states the creation action and does not reveal side effects, return behavior, account handling (e.g., default account use), or permission needs, which are important for a mutation tool.

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 states the action and key optional fields with no noise. Every word adds value, achieving high conciseness without fluff.

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?

The tool is a simple creation operation, but with no output schema and no annotations, the description needed to clarify what happens after creation (e.g., return value) and how account selection works. The current text is too minimal, leaving the agent without guidance on account usage or possible side effects.

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 50% (name and account have descriptions; email and phone do not). The description adds that email and phone are optional contact fields, helping clarify two undocumented parameters, but it omits the account parameter entirely and does not add format details. This partially compensates for the schema gaps.

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 explicitly states 'Create a new contact' with a specific verb and resource, and differentiates from sibling tools like google_contacts_list and google_contacts_search by focusing on creation. It further specifies the core fields (name and optional email/phone), making the intent unmistakable.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites like account selection or any conditions under which to prefer another tool. It simply states the action without contextual direction.

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