create_voicememo_message

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

Annotations indicate readOnlyHint=false and destructiveHint=false, signaling a non-destructive write operation. The description merely restates the creation action without additional behavioral details like permissions, side effects, or response behavior, adding minimal value beyond the annotations.

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 concise with two sentences: the first states the purpose, and the second adds a key requirement. It is front-loaded and wastes no words.

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?

The description lacks explanation for the audio_file, folder_id, and workspace_id parameters, and does not clarify what a VoiceMemo message is or how it differs from other message types. Given 5 parameters and no output schema, the description fails to provide sufficient context for correct tool usage.

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 coverage is 100%, so parameters are individually documented. The description adds an important constraint not present in the schema: that at least one of 'transcript' or 'links' must be provided. This clarifies a conditional requirement, enhancing parameter semantics despite omitting audio_file and folder/workspace constraints.

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 'Create a VoiceMemo Message' with a specific resource type. However, it does not distinguish this tool from siblings like create_conversation_message or create_direct_message beyond the name, leaving ambiguity about what makes a VoiceMemo unique.

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 a conditional requirement ('you must provide a transcript or link attachments'), which helps guide usage. However, it does not offer guidance on when to use this tool versus alternatives, such as when to create a voice memo instead of a regular message.

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