stop_all_template_tasks

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It states only that it stops all running tasks and returns an empty dict, but does not disclose side effects (e.g., what happens to dependent tasks), required permissions, or behavior when no tasks are running.

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 very concise and front-loaded, with the core purpose in the first sentence. However, it could benefit from slightly more context without excessive verbosity.

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 tool with no annotations and a simple output schema, the description is minimally acceptable but incomplete. It lacks usage guidelines and parameter details, which are important for correct invocation. The output is well-described, but the overall context is insufficient.

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 input schema has 0% description coverage for parameters. The description merely lists parameter names ('project_id: ID of the project', 'template_id: ID of the template') without adding any meaning beyond the schema (types are integer). It does not explain how to obtain these IDs or any constraints.

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 'Stop all running tasks for a template', which is a specific verb ('Stop') and resource ('all running tasks for a template'). It effectively distinguishes from sibling tools like 'stop_task' (single task) and 'bulk_stop_tasks' (likely multiple templates).

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 is provided on when to use this tool versus alternatives (e.g., stop_task for a single task, bulk_stop_tasks for multiple templates). The description lacks context about prerequisites or conditions for usage.

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