contacts_start_recording

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

The description is a bare phrase with no annotations to compensate. It does not disclose side effects, idempotency, whether recording is ongoing, or what happens if recording is already active. 'Start' implies a mutation but omits any safety profile or behavioral context.

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 short, which is concise but under-specified. It front-loads the action but fails to include any supporting context needed for correct invocation, making it more under-specification than effective conciseness.

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 three parameters and no annotations, the description is inadequate. While an output schema exists, the behavioral semantics (e.g., what 'recording' entails, whether it requires an ongoing call, or how the voice_recording parameter affects behavior) are completely absent, leaving the agent to guess.

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%, and the description adds no meaning to parameters such as instance_id, contact_id, or voice_recording. The schema itself provides basic types and defaults, but the description does not clarify their roles, constraints, or the effect of the voice_recording flag.

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 uses the verb 'start' with the object 'contact recording', clearly indicating that the tool initiates recording for a contact. It distinguishes from sibling tools like 'contacts_stop_recording' and 'contacts_start_outbound_voice' by specifying recording rather than a call or task.

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 alternatives. It does not mention prerequisites (e.g., an active contact or call), nor does it contrast with related tools like 'contacts_stop_recording' or 'contacts_start_chat'.

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