Retrieve delegated tasks newest first, optionally filtered by session or state, to track progress and find items needing input.
Find the tasks you delegated again, newest first, optionally only a session's or only one state (e.g. input-required).
| Name | Required | Description | Default |
|---|---|---|---|
| state | No | only tasks in this state, e.g. input-required | |
| session_id | No | only this session's tasks |
| Name | Required | Description | Default |
|---|---|---|---|
| tasks | Yes | newest first |
Changes observed during successful MCP inspections.
v0.1.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Since no annotations are provided, the description must carry all behavioral context. The specification 'newest first' is a crucial behavioral trait regarding the sorting and return order that is not captured in the input schema, providing significant value to the AI agent.
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 description is highly efficient, using a single, well-structured sentence to convey the core function, sorting behavior, and optional filtering criteria.
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 that an output schema exists, the description provides maximum necessary context for successful tool invocation by defining the scope, constraints, and inherent sorting behavior of the resulting list. It is complete for a read-only list operation.
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?
With 100% schema coverage, the description's role is supplementary. It provides helpful human context for the parameters, defining 'state' as requiring an example ('input-required') and clarifying the focus on 'session' vs. general tasks.
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 defines the resource ('tasks you delegated') and the operation ('Find'), making it unambiguous. The context implies this tool retrieves tasks assigned to the current user by another party, effectively distinguishing it from other list-type siblings.
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 guides the user on how the tool should be constrained by the caller by describing the optional filtering logic ('optionally only a session's or only one state'). This helps the agent determine the necessary scope for the API call.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.