voicebox_update_profile

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

Since no annotations are provided, the description carries the full burden. It discloses partial update behavior ('Only provided fields are changed') and the API requirement for the name field, including automatic fetching. However, it does not mention permissions, side effects, or response details.

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?

Three sentences, front-loaded with the main action, each sentence adds important information without redundancy or fluff.

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 the tool has 5 parameters, 1 required, an output schema, and many siblings, the description covers the key behavioral nuance about name handling and partial updates. It does not explain when to use this vs update_profile_effects, but the output schema likely covers return values. Adequate for an agent to use 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?

Schema coverage is 100%, so baseline is 3. The description adds value by explaining the name field's API requirement and automatic preservation, enhancing the schema's description which only states 'if null, keeps current name'.

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 explicitly states 'Update voice profile settings' which is a specific verb+resource. It distinguishes from sibling tools like voicebox_update_profile_effects by focusing on general settings, not effects.

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?

Provides guidance on the name field requirement and automatic preservation, but does not explicitly state when to use this tool versus alternatives like voicebox_update_profile_effects or voicebox_get_profile.

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