androidapi_create_contact

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

Annotations already indicate this is a write operation (readOnlyHint=false) with potential external effects (openWorldHint=true). The description adds no further behavioral details such as authentication requirements, data persistence, or side effects beyond creating the contact.

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?

Extremely concise at 12 words. The single sentence is front-loaded with the action and leaves no room for filler. Every word 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?

Lacks information about return values (e.g., contact ID) and error conditions. For a creation tool without an output schema, the description should ideally clarify what the agent can expect after calling. The openWorldHint annotation suggests side effects, but no details are provided.

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 100%, so the input schema already documents all three parameters. The description adds minimal value, only restating that groups are assigned. No additional semantics 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's function: 'Create a new contact and assign it to one or more groups.' It uses a specific verb (create) and resource (contact), and distinguishes itself from sibling read/search tools like androidapi_get_contacts.

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 explicit guidance on when to use this tool versus alternatives. While it is the only contact creation tool among siblings, there are no prerequisites or scenarios mentioned. The context of sibling tools does not provide a clear usage boundary.

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