get_tasks_toolRetrieve all tasks from the task repository system. Filter by parent ID to fetch related subtasks.
Retrieve all tasks from the task repo system.
| Name | Required | Description | Default |
|---|---|---|---|
| parentId | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds nothing beyond that — no pagination behavior, no scoping rules, and 'all tasks' is mildly misleading given an optional parentId filter. With annotations carrying the load, the description still contributes almost no behavioral context.
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?
One short, front-loaded sentence with no wasted clauses. It is efficient, though 'from the task repo system' is vague filler that adds no actionable meaning.
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?
An output schema exists so return values need not be explained, but for a tool with an optional parentId filter that is undocumented everywhere, the description leaves a real gap: an agent cannot tell whether omitting parentId returns a global list or a subtree. It should clarify the scoping semantics of that parameter.
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 single parentId parameter is undocumented in both schema and description. 'Retrieve all tasks' actively suggests no filtering, which obscures rather than explains the parentId argument's purpose.
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?
States a specific verb ('Retrieve') and resource ('tasks'), clearly telling an agent what the tool returns. However, it offers no differentiation from siblings like get_user_stories, create_task, or update_task_status, and the word 'all' conflicts with the fact that a parentId filter exists.
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 on when to use this versus the sibling read tools (get_user_stories, get_requirements) or the task mutation tools. The 'all tasks' phrasing implies an unfiltered dump but never explains what parentId does or when to pass it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.