set_assignment_audio_recording

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

With no annotations, the description carries the burden of behavioral disclosure. It correctly signals that this is a mutating operation and mentions permission requirements and a confirmation guard. However, it does not describe side effects, reversibility, idempotency, or what happens once the flag is set.

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 two sentences with no filler. The action is front-loaded, and the second sentence adds essential preconditions. Every word earns its place.

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 with 4 parameters, 0% schema coverage, no annotations, and no output schema, the description is too sparse. An agent cannot reliably determine how confirm_assignment_id should be used, what enabled controls, or how profile affects the call.

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%, so the description must compensate for missing parameter explanations. It only vaguely references 'exact assignment confirmation', which maps to confirm_assignment_id, but it does not explain enabled semantics, the role of profile, or the requirement that confirmation must match assignment_id.

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 a specific verb ('Set'), a specific resource ('assignment audio-recording flag'), and the operation's nature. It also distinguishes itself from related siblings such as get_assignment_audio_recording (read vs. write) and set_questionnaire_audio_recording (assignment vs. questionnaire).

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 provides clear context by naming required permissions (fieldwork_write/admin_write) and a safety prerequisite (exact assignment confirmation). It does not explicitly name alternatives or exclusions, but the context is strong enough for an agent to understand when this write operation applies.

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