aiworkhub_task_template_list

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

readOnlyHint=true already covers the safety profile, so the description's contribution is the scoping claim that results are limited to the current repository and 'bounded'. That is real added context, but 'bounded' is never explained (cap? pagination? truncation?) and no ordering or empty-registry behavior is described.

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?

A single front-loaded sentence with no wasted clauses. Slightly marred by the stacked jargon 'bounded repository-bound', which costs clarity without adding information.

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?

With no inputs and an output schema present, the definition is close to sufficient, but 'bounded' and the manager-only framing are left unexplained, and it does not point at the natural follow-up (aiworkhub_task_template_show / aiworkhub_task_create_from_template) after listing.

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 tool takes zero parameters, so the baseline is 4 and there is nothing for the description to clarify. It introduces no conflicting or missing parameter notions.

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?

Specific verb+resource: 'list the ... template registry', so an agent knows this enumerates task templates. The 'repository-bound' qualifier narrows scope meaningfully. It never names or distinguishes itself from the closest sibling, aiworkhub_task_template_show (single-template read), so it stops short of 5.

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?

'MANAGER READ:' hints at the intended audience/mode, but there is no statement of when to choose this over aiworkhub_task_template_show or aiworkhub_manager_recipe_list, and no preconditions or exclusions. Usage context is implied at best, not stated.

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