List saved workflow templates

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds useful context beyond the annotations: it lists only user-saved Aidoo templates, not Odoo automations, and specifies the intended call order after aidoo_context. It does not discuss empty results or pagination, but the output schema likely covers return shape.

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?

Three short sentences, each carrying distinct information: when to call, what it lists, and what it is not. The key instruction is front-loaded, and there is no filler or redundant restating of the title.

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 zero parameters, an output schema present, and read-only/idempotent annotations, the description covers call placement, trigger conditions, and data scope. Nothing essential for selecting or invoking this tool correctly is missing.

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 has zero parameters, so the description has nothing further to add about parameter syntax or meaning. Schema coverage is trivially 100%, and the description's phrase 'all workflow templates' clarifies the implicit scope of the empty argument list. Baseline 4 is appropriate here.

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 uses a specific verb ('Lists'), a concrete resource ('all workflow templates saved by the user in Aidoo'), and explicitly scopes it to Aidoo, not Odoo. It clearly differentiates the tool from Odoo's ir.actions and base.automation, making its purpose unambiguous.

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 explicitly instructs to call the tool 'right after aidoo_context' and states the trigger condition: when a user asks to run a workflow or task they saved before. It also gives a clear exclusion by saying the answer is not found in Odoo's ir.actions or base.automation, giving strong routing guidance.

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