Get a TTS clip

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

Annotations already declare readOnlyHint=true, and the description adds conditional disk-writing behavior, which is a local side effect not covered by annotations. It discloses when download happens and the dependency on API response shape ('when the API returns a URL or audio payload'), providing valuable context beyond annotations.

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?

Two sentences, front-loaded with the primary action. No redundant phrases or filler; every word earns its place.

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 covers core fetch and conditional download behavior, but lacks guidance on return value/status, error handling, or the role of filename/output_dir. Without an output schema, the agent is left guessing the response format and how to use the optional parameters.

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 descriptions cover clip_id and download, but filename and output_dir have no descriptions. The description does not explain these parameters or their defaults; it only mentions 'save its audio to disk' without specifying the filename/output_dir semantics. This leaves 50% of parameters under-specified.

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?

States 'Fetch the status/metadata of a clip by id' – a specific verb and resource with clear scope. The conditional download behavior is also described. This clearly distinguishes from sibling 'wellsaid_list_clips', which lists clips, and 'wellsaid_create_clip_async', which creates them.

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?

Implies usage from 'by id' and references 'wellsaid_create_clip_async' in the schema, indicating it's for a single clip from creation. However, it does not explicitly contrast with alternatives like 'wellsaid_list_clips' or state when download should or should not be used.

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