tasks_list

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

No annotations provided, so description bears full burden. It explains behavior for 'responsible' role and 'self_note' field, but lacks details on read-only status, rate limits, or error conditions.

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 concise with multiple sentences, each adding value. Front-loaded with main purpose. Slight ambiguity around 'self_note' field, but overall efficient.

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 an output schema exists, return values need not be explained. However, important context like the effect of 'include_done' and 'user_id' is missing. The description covers role behavior but not other parameters.

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 only 25%. The description mentions 'self_note' but this is not a parameter. No additional meaning is added for 'limit', 'user_id', or 'include_done' beyond the schema 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?

The description clearly states 'Tasks of a person in the selected role', which matches the tool name. It adds nuance about default role and self-notes, but does not explicitly distinguish from sibling tools like 'task_get' or 'tasks_updates'.

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?

Provides context on when to use different roles (e.g., default 'responsible' for personal tasks, managers need role to avoid noise), but does not compare to alternatives or specify when not to use this tool.

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