save_contact

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

The description mentions that saving notifies the profile owner, adding behavioral context beyond the openWorldHint annotation. However, it does not detail side effects like permissions or potential conflicts.

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 sentences, front-loaded with action and context, and contains no unnecessary words. It is efficient and easy to parse.

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, the description omits return value details. It does not cover error handling or conditions like duplicates. While adequate, it leaves gaps for a save operation with 5 parameters.

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 100%, so all parameters are described in the schema. The description only adds minimal emphasis on required fields (name, email) but does not provide additional meaning for optional parameters like notes or phone.

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 tool saves contact information after interacting with a PingRep AI Representative, specifying the action and resource. It distinguishes from sibling tools like list_my_contacts and get_contact by emphasizing the act of saving and connecting.

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 indicates the tool should be used after interacting with a rep and requires name and email. It provides clear context for when to use but does not explicitly exclude scenarios or suggest alternatives.

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