updateRelationship

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

No annotations provided, so the description must convey behavioral traits. It only states 'Update' implying mutation, but fails to disclose side effects, required permissions, or data integrity implications, which are critical for a write operation with 7 parameters.

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 extremely concise (single sentence) but at the expense of completeness. It lacks structure, no paragraph breaks, and fails to provide any additional context beyond the tool name. Under-specification reduces its utility.

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 absence of annotations, partial schema coverage, no output schema, and 7 parameters, the description is far from complete. Critical information about update behavior, parameter constraints, and return values is missing.

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 only 29% (2 of 7 parameters have descriptions). The description adds no parameter-level information, leaving most parameters (firstName, lastName, emails, etc.) semantically opaque. Parameter semantics are insufficiently addressed.

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 'Update a relationship contact' clearly states the action (update) and the resource (relationship contact), distinguishing it from siblings like createRelationship, deleteRelationship, getRelationship. However, it lacks detail on what specific aspects can be updated.

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?

No guidance on when to use this tool versus alternatives such as createRelationship, deleteRelationship, or other update tools. No context on prerequisites or when not to use, leaving the agent without decision support.

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