retry_task

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

Description reveals that retrying clears the fault and re-queues the task on next CPE inform, adding context beyond annotations (which indicate destructive and non-idempotent). No contradiction with 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?

Description is concise with clear sentences, includes an example and limitations, but could be slightly shorter by removing redundant phrases. Still well-structured.

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?

Given single parameter, no output schema, and annotations covering safety, the description fully covers purpose, usage, parameter semantics, and limitations. No gaps.

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?

Parameter schema has 100% coverage, but description adds value by explaining task_id is the _id field, how to obtain it, and includes an example. Schema alone doesn't provide this context.

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 'Retry a faulted task in GenieACS' with specific verb and resource, and distinguishes from sibling tools like delete_task and connection_request.

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?

Explicitly says when to use (after a faulted task), when not to (non-faulted tasks), and provides context to obtain task_id and check fault information via genieacs://faults/{id}.

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