breeze_add_personWRITE: create a new person profile with a first and last name, and optionally set profile fields in the same call (same field shape as breeze_update_person). Check breeze_list_people first to avoid duplicates. Returns the new profile including its id. Breeze: GET /api/people/add.
| Name | Required | Description | Default |
|---|---|---|---|
| last | Yes | Last name. | |
| first | Yes | First name. | |
| fields | No | Profile fields to set (sent as fields_json). |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only supply destructiveHint=true, so the description carries most of the burden and does well: it declares the write nature, that fields can be set in the same call, and that the new profile including its id is returned. It stops short of stating auth requirements or whether a partial failure rolls back the create.
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?
Dense and front-loaded: the operation type, required inputs, optional behavior, precondition, and return value each get roughly one clause. The trailing 'Breeze: GET /api/people/add' is minor implementation trivia, and a 'GET' endpoint for a write is slightly odd, but it costs no real space.
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?
Covers the essentials for a create tool: inputs, optional field-setting, a duplicate-avoidance precondition, and the return shape (profile with id), with no output schema to compensate for. Missing notes on permissions/failure behavior keep it from being fully complete.
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 already 100%, so the baseline is 3; the description exceeds that by pointing at breeze_update_person as the field-shape reference, which is genuine meaning not present in the schema. It adds nothing about the required first/last params, but those are self-explanatory.
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?
Opens with an explicit operation marker ('WRITE: create a new person profile') naming the verb and resource, and enumerates the required fields (first/last) plus optional profile fields. An agent can immediately distinguish it from breeze_update_person and the other breeze_add_* tools.
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?
Gives a concrete precondition: 'Check breeze_list_people first to avoid duplicates,' which names the sibling tool to consult before calling. It also cross-references breeze_update_person for field shape, but does not state when *not* to use this tool (e.g. if the person already exists) beyond the duplicate warning.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.