Create Contact

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

With no annotations provided, the description carries the transparency burden. It discloses a permission requirement (SUBREG_READONLY=false), which is a useful behavioral trait, but it does not mention side effects, error behavior, or response format. This is better than no disclosure but still leaves significant gaps for a mutating operation.

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 concise at two sentences, front-loaded with the purpose, and contains no redundant information. The external reference is presented as a single line, keeping the description focused.

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 complex due to the nested 'params' object and the absence of an output schema. The description does not explain what the create operation returns or what happens on success/failure, relying on an external manual. This leaves the agent under-informed for invoking the tool and processing the response.

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?

The input schema defines only an opaque 'params' object with no internal properties, so schema coverage is 0%. The description compensates by listing example fields (name, email, address, phone) and directing to the full Subreg schema, adding meaningful semantic guidance beyond the empty 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 'Create a new contact object' with a specific verb and resource. This distinguishes it from sibling tools like update_contact and info_contact, which target different actions on the same resource.

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 a prerequisite ('Requires SUBREG_READONLY=false') which gives some context for when the tool is usable, but it does not explicitly discuss when to use this tool versus alternatives such as update_contact. The usage is implied by the verb 'create' rather than explicitly differentiated.

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