all_tasks

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

With no annotations provided, the description must carry the burden of behavioral disclosure, but it only says tasks are 'aggregated'. It does not explain whether excluded tasks are hidden by default, how aggregation is computed, or whether this is a read-only operation.

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 phrase is concise and front-loaded, with no wasted words. However, it is more of a fragment than a complete specification, and its brevity contributes to ambiguity rather than clarity.

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?

Despite having an output schema and only one optional parameter, the description omits parameter behavior and any usage context. An agent can infer the basic purpose but not enough information to confidently invoke the tool correctly in all situations.

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 the description does not mention include_excluded at all. The schema's title and default value offer some self-explanation, but the description fails to add meaning beyond the schema.

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 'Toutes les taches agregees du vault' communicates that the tool returns all aggregated tasks in the vault, but it is a noun phrase without an explicit verb such as 'list' or 'get'. It does not clearly distinguish this tool from the sibling 'tasks_for' or other task-related tools.

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?

There is no guidance about when to use this tool versus alternatives like 'tasks_for' or search tools. It also does not mention the include_excluded parameter or any context that would help an agent decide to call this tool.

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