Get a voice profile

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does disclose the key behavior of returning an error when no profile exists, and it implies a read-only operation. However, it does not mention authentication requirements, side effects, or any details about the returned voice profile structure.

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 a single, focused sentence that front-loads the main action and includes the key error case. Every word contributes value and there is no redundancy.

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 simple one-parameter read tool, the description is mostly adequate. However, since there is no output schema, it would benefit from specifying what a voice profile contains or at least referencing its structure. The error case is covered, but the return value remains vaguely defined.

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?

The schema provides no description for the userId parameter, but the description's phrase 'for a user' connects the parameter to its purpose. Since there is only one required parameter and its name is self-explanatory, the description adds enough meaning despite 0% schema coverage.

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 ('Returns the voice profile'), the target resource ('for a user'), and the error condition ('or an error if none exists yet'). This makes the tool's purpose obvious and distinguishable from siblings like set_voice_profile and bootstrap_voice_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 clearly establishes that this tool is for retrieving an existing voice profile, which implies the read use case. It does not explicitly name alternatives or exclusion criteria, but the retrieval framing provides clear context.

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