set_task_timeout

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

No annotations provided, so description must fully disclose behavior. It only says 'change' but does not explain if limits are set relative or absolute, if changes require restart, or if they are reversible. Lacks details on what happens to current timeout.

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 a single sentence, which is concise but omits necessary detail. It is minimally adequate for the purpose but too brief for a 4-parameter tool with 0% schema coverage.

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 no annotations, 0% schema coverage, and 4 parameters, the description is incomplete. It does not explain return values (though output schema exists) or side effects. A mutation tool needs more context for safe invocation.

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 description coverage is 0%, and description adds no meaning for parameters. The term 'soft' and 'hard' are ambiguous; description does not clarify their units, meaning, or defaults.

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?

Description clearly states the tool changes soft and hard time limits for a task on a worker. It is specific about the verb and resource, and distinguishes from siblings like set_task_rate_limit, though it could be more explicit about soft vs hard definitions.

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?

No guidance on when to use this tool vs alternatives (e.g., set_task_rate_limit, abort_task). No mention of prerequisites, side effects, or scenarios where it is inappropriate.

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