restore_relationship

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

Without annotations, the description discloses creation of a restoration observation (priority 1001) and immutability for audit. However, it omits side effects, permissions, or failure conditions (e.g., if relationship not found).

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?

Three sentences, each adding unique information: purpose, mechanism, and audit property. No redundant or irrelevant content.

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 annotations and no output schema, the description effectively explains what the tool does and its audit trail. Lacks error handling or result details, but sufficient for basic usage.

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. Description adds minimal value beyond schema, only noting reason as optional for audit and user_id inference. Does not clarify parameter constraints beyond the 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 it restores a deleted relationship, differentiating from create_relationship and delete_relationship. It specifies the mechanism (restoration observation) and effect (visible again).

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 implicitly indicates use after deletion, but does not explicitly exclude scenarios like restoring an already active relationship or provide alternatives. Clear context but lacks explicit when-not-to-use.

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