create_voice_profile

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

Annotations indicate a write operation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds behavioral context: it requires an active skill grant/run descriptor and rejects direct calls, and it requires 1-3 authorized audio samples. This goes beyond the annotations and informs the agent of preconditions.

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, front-loaded with the core purpose, and includes a critical prerequisite. Every word contributes; no wasted content.

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 gives the essential purpose and a key precondition, but with seven parameters and no output schema, it lacks details on return values, error cases, and the role of optional parameters. It is adequate but not fully complete for a tool of this complexity.

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 carry parameter meaning. It clarifies sampleAssetIds as '1-3 authorized project audio samples' but does not explain the other six parameters like language, voicePrompt, idempotencyKey, tags, etc. This leaves significant ambiguity for the agent.

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 tool's function: 'Create a reusable project voice profile from 1-3 authorized project audio samples.' It uses a specific verb 'create' with a clear object and source constraint, distinguishing it from siblings like run_skill.

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 explicit usage guidance: 'Call run_skill first' and 'This tool rejects direct calls without the active skill grant/run descriptor.' This tells the agent when to use the tool (after run_skill) and when not to (direct calls without grant). It doesn't mention alternatives, but the sequential dependency is clearly stated.

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