contacts_stop_recording

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

With no annotations provided, the description needs to disclose side effects, prerequisites, and failure behaviors. It merely says 'Stop contact recording' without explaining what happens to the contact, whether recording must be active, or whether the operation is reversible. This is a significant gap.

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 a single concise sentence with no unnecessary words. It is front-loaded with the action, but it could be considered under-specified. However, for conciseness alone, it is efficient.

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 mutation tool with two required parameters and an output schema, the description is inadequate. It does not explain the workflow, any prerequisites, or the effect on the contact. Given the lack of annotations and parameter details, the description is far from complete.

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 0%. The description provides no meaning for the parameters instance_id and contact_id beyond their names. It does not clarify what types of values are expected or how they relate to the recording operation.

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: stopping contact recording. It identifies the specific resource (contact recording) and the verb (stop). However, it does not differentiate from sibling tools like contacts_stop, which could be ambiguous, so it doesn't fully earn the highest score.

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?

There is no guidance on when to use this tool versus alternatives such as contacts_stop or contacts_start_recording. The description provides no context for when stopping recording is appropriate or any exclusions.

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