ss_contact_save

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

No annotations are provided, so the description carries the full burden. It states the tool 'creates or updates', which indicates a write operation, but does not disclose behavioral details such as whether it is idempotent, required permissions, or what happens on conflict (e.g., does it always return a new ID?). The return of a contact ID is mentioned but without further context.

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 sentence that is clear, to the point, and contains no redundant information. 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?

Given the 11 parameters (7 required) and no output schema, the description adequately explains the tool's purpose and what it returns. However, it could be more complete by noting that it uses upsert semantics (create or update) and perhaps that it is the primary tool for setting contact details before domain operations.

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%; all parameters have descriptions in the schema. The tool description adds no extra meaning beyond what is already in the schema, so baseline of 3 is appropriate.

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 verb 'Create or update' and the resource 'contact', and specifies the output ('contact ID') and the use case ('for domain registration/transfers'). This distinguishes it from sibling tools like ss_contact_get or ss_contact_attr_save.

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 implies usage for domain registration/transfers but does not provide explicit guidance on when to use create vs update, or when to use this tool over alternatives like ss_contact_get. No when-not-to-use or prerequisites are mentioned.

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