contacts_stop

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

With no annotations present, the description carries the full burden of behavioral disclosure. It only states 'End a contact' without mentioning side effects, whether the contact must be active, or if the action is irreversible.

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 (two words) with no wasted words, but it is under-specified. It is not appropriately sized for a tool that would benefit from explaining the scope of 'end'.

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?

For a mutating tool with no annotations, this description is incomplete. It fails to explain what ending a contact entails, whether it is safe, or how it relates to sibling tools, making it difficult for an agent to invoke correctly.

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?

The schema defines two parameters (instance_id, contact_id) with no descriptions, and the tool description mentions neither parameter. The description adds no meaning beyond the parameter names themselves.

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 'End a contact' uses a specific verb and resource, which is clear at a basic level and distinguishes this from start/transfer tools. However, it is essentially a synonym for the tool name 'contacts_stop', adding little new information and not detailing what 'end' encompasses.

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 is provided on when to use this tool versus related tools such as contacts_stop_recording or contacts_transfer. The description lacks any context about the contact lifecycle, prerequisites, or alternatives.

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