add_contact

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

With no annotations provided, the description carries the full burden. It reveals the upsert behavior (updates if number exists). But it does not disclose authorization requirements, rate limits, or error conditions. The behavioral info is minimal beyond the basic functionality.

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?

Two sentences, front-loaded with the core purpose, followed by key behavior (upsert). No wasted words. All sentences are necessary.

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 has 10 parameters, no output schema, and no annotations. The description is too sparse to fully inform an agent. It lacks details about return values, error handling, and the behavior of optional fields. More context is needed for an agent to use it confidently.

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 baseline 3. The description does not add new meaning to any parameter beyond what the schema already provides. It only reiterates that list_key and number are required.

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 action: adds a new contact to an existing agenda. It specifies the verb 'agrega' and the resource 'contacto a una agenda'. Also mentions update behavior if number exists, distinguishing it from mere insertion.

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 lists required fields (list_key and number), which is a basic prerequisite. However, it does not provide guidance on when to use this tool versus siblings like add_loyalty_contact or add_wallet_contact, nor does it mention when not to use it.

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