Contact Create

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

The annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, covering the safety profile. The description adds the validation rule that at least a name or email is required, which is useful but does not disclose duplicate handling, permission requirements, or other behavioral traits beyond what annotations and schema provide.

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 two short sentences with no wasted words. It is front-loaded with the core action ('Create a contact') and immediately follows with the essential input requirement, making it easy to parse quickly.

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 tool's simplicity, 100% schema description coverage, and clear annotations, the description is nearly complete for basic invocation. It could mention that this is for new contacts only (e.g., not for updating existing contacts), but for a create operation with no output schema, the essential information is present.

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 100%, so the parameter-level documentation already explains each field. The description adds a cross-parameter constraint not present in the schema—'Provide at least a name or an email address'—which meaningfully affects invocation since only organizationId is marked required. This extra business rule is valuable 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 states a specific verb and resource: 'Create a contact.' It clearly identifies the operation as a creation. However, it does not explicitly distinguish this tool from contact_update or other sibling tools, so it falls short of a 5.

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 contact_create versus alternatives such as contact_update or contact_list. The only instruction, 'Provide at least a name or an email address,' is an input constraint rather than usage context, and no exclusions or scenarios are mentioned.

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