Create a new user in the database using name, email, address, and phone, then persist the record to a local JSON file.
Create a new user in the database
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| Yes | |||
| phone | Yes | ||
| address | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already convey the safety profile (readOnlyHint false, destructiveHint false, idempotentHint false), and the description only restates the obvious 'create' operation, adding no extra context such as authentication needs, side effects on duplicate emails, or return behavior. This is a missed opportunity to disclose meaningful behavioral traits beyond structured data.
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 core purpose without wasted words. It is appropriately concise for a simple tool, though it lacks substance that could be included without becoming verbose.
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 no output schema, four required parameters, and a mutation operation, the description should at least mention what the tool returns upon success, how errors (e.g., duplicate email) are handled, or any required permissions. None of this is present, leaving significant gaps for an agent to make safe and correct calls.
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?
With 0% schema description coverage and no parameter details in the description, the agent receives no semantic information about name, email, address, or phone beyond their obvious string names. The description does not compensate for the schema's silence, failing to explain formats, constraints, or required combinations.
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 'Create a new user in the database' uses a specific verb and resource, clearly indicating a create operation. It does not explicitly differentiate from the sibling tool 'create-random-user', though the meaning is implicitly distinct (this creates a specific user, the sibling creates a random one).
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 is provided about when to use this tool versus create-random-user. The description implies a use case for adding a specific user, but it does not state conditions, prerequisites, or mention the alternative, leaving the decision to the agent's inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.