save_profile

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

With no annotations, the description carries full burden. It discloses important side-effects: shadowing built-in names, mapping to generate_speech knobs, and seed-locked consistency. It does not mention permissions or idempotency, but the disclosed behaviors go well beyond a bare 'save profile' statement.

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 well-structured with a purpose paragraph, a context paragraph, and an Args list. It is as long as needed for 11 parameters, with no filler or redundant repetition of schema defaults.

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 complex 11-parameter tool with no annotations and no output schema, the description covers the tool's purpose, usage relationship, parameter semantics, and a key side-effect (shadowing built-ins). It provides everything an agent needs to invoke it 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 0%, and the description fully compensates by documenting all 11 parameters in the Args section with types, examples, and value constraints (e.g., stability accepts 'creative'/'natural'/'robust' or 0-1, seed range 0-4294967295). This adds real meaning beyond the raw schema.

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 opens with a specific verb+resource: 'Save a reusable speech profile (a persona/mood preset)'. It clearly distinguishes from siblings by explaining that profiles bundle delivery settings so generate_speech(profile="<name>") reproduces them, contrasting with voice/speaker save tools.

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 clear context on when to use: to create reusable presets for generate_speech. Explains design choices (pin voice+seed vs voice-agnostic mood) and warns about shadowing built-in profiles. Does not explicitly name alternative tools, but context implies this is for speech presets, enough to guide selection.

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