voicebox_export_profile

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

No annotations are provided, and the description does not disclose behavioral details such as whether the export is destructive, permissions required, or the format of the output. It only states that data can be imported later, lacking transparency about side effects or constraints.

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 consists of two concise sentences with clear front-loading of the primary action, followed by a useful note about the import counterpart. No unnecessary information.

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 a single parameter and existence of an output schema, the description adequately covers the tool's purpose and relationship to the import tool. Some detail about the output format or behavior is missing but likely covered by the output schema.

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% for the single parameter (profile_id), and the description adds minimal extra meaning. The parameter is mentioned in context but not elaborated beyond the schema's own description.

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 'Export a voice profile with all its samples and settings,' which is a specific verb (export) and resource (voice profile) with defined scope. It distinguishes from sibling tools like voicebox_import_profile and voicebox_get_profile.

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 links to the complementary import tool, indicating a typical use case. However, it does not explicitly state when not to use this tool or provide alternative approaches for partial exports.

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