speechify_retry_job

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure, and it discloses almost nothing. It doesn't say whether retrying mutates the original job or creates a new one, whether a new job id is returned, whether the operation is idempotent, or what permissions are needed. For a state-changing tool this is a substantial gap.

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?

One short sentence with no filler and the precondition front-loaded, so nothing is wasted. However, it is undersized for a mutation tool — brevity here comes at the cost of specification rather than from efficient writing.

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?

No annotations, no output schema, and an entirely undocumented required parameter mean the description should do more work than a single clause. An agent still cannot tell what a successful retry returns or how to recover from an invalid job_id.

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 single required parameter job_id is never mentioned in the description. The agent must infer that job_id is the identifier of the failed/cancelled job it wishes to re-run, and nothing explains the expected format or where to obtain it.

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?

"Retry" is a specific verb, but the resource is described as "upload work" rather than the job entity that the tool name and parameter imply. The agent can infer it re-runs a previously failed job, but the description never uses the word "job" and so does not map cleanly onto siblings like speechify_get_job or speechify_cancel_job.

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?

It supplies a real precondition — only for work that is failed or cancelled — which implies when to call it. It does not say how to discover a failed job (e.g., list_jobs/get_job to obtain a job_id), nor does it state that cancel_job or upload_text are the alternatives for the other states.

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