delete_relationship

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

Describes side effects (deletion observation, exclusion from snapshots/queries), audit immutability, and error response (404 with discovery hint). No annotation contradicts.

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?

Few sentences, each essential: action, prerequisite, behavioral effect, error handling. Front-loaded with core action.

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 full schema and no output schema, description explains return behavior and side effects completely. No gaps for an agent to make errors.

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 covers 100% of parameters. Description adds value by specifying that relationship_type must be exact and advising to discover it via list_relationships if unknown.

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?

Clearly states 'Delete a relationship' – a specific verb and resource. Distinguishes from sibling tools like 'create_relationship' and 'restore_relationship' by mentioning immutability and audit trail.

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?

Explicitly instructs to use list_relationships first when relationship_type is unknown. Provides clear preconditions and what to do in case of no match (404 hint).

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