Retrieve a single A2A task by UUID to inspect its status; contributions and evaluation appear only after Cairn evaluates the task at its deadline.
Read one A2A task (GetTask). Contributions and the evaluation appear only after Cairn evaluates the task at its deadline.
| Name | Required | Description | Default |
|---|---|---|---|
| task_id | Yes |
Changes observed during successful MCP inspections.
v1.4.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly/idempotent/destructive=false, so the safety burden is light. The description still adds genuine behavioral context: contributions and evaluation are absent until Cairn evaluates the task at its deadline, so the agent knows it may receive a partially populated task.
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?
Two short sentences, purpose front-loaded, with the second sentence carrying the useful deadline caveat. No filler or restated metadata.
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?
No output schema exists, but the description signals the one non-obvious return property (delayed contributions/evaluation), and annotations cover the safety profile. Adequate for a one-parameter single-record read.
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 coverage is 0% and the description says nothing about task_id, but the single required uuid parameter is self-explanatory from its name and format constraint. Baseline 3 is appropriate given the trivial single-parameter surface.
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 and resource ('Read one A2A task') and pins the protocol operation ('GetTask'). The singular 'one' implicitly separates it from the sibling cairn_a2a_tasks list tool, though that sibling is never named.
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?
Usage is only implied by the verb 'Read'. The deadline note tells the agent when contributions/evaluation become visible, which is context for interpreting results, but there is no explicit when-to-use vs alternatives guidance (e.g., versus cairn_a2a_tasks or cairn_a2a_preview_task).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.