get_task_full

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

No annotations are provided, so the description carries the burden. It does disclose the payload breadth ('everything', 'whole conversation and all outputs'), which implies a read-only retrieval, but it never states that it is non-mutating, says nothing about permissions or whether it errors for tasks not owned by the caller, and leaves polling/side-effect behavior implicit.

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 with the payload scope front-loaded and no redundant restating of the tool name. The second sentence is terse to the point of being cryptic, but it earns its place as the only usage signal.

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-shape detail is unnecessary, and with one parameter the surface is small. However, with zero annotations the description should at least confirm this is a safe read and clarify the 'not to wait' alternative; it does only the former implicitly and the latter not at all.

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 single required parameter task_id is never mentioned in the description. The phrase 'delegated or assigned to you' loosely bounds which task IDs are valid, but format, source, and failure behavior for an invalid ID are undocumented in both schema and description.

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 ('get') and resource ('a task') plus the scope of the return payload: the whole conversation and all outputs. It also scopes to tasks 'delegated or assigned to you', which helps separate it from the many list/update siblings, though it never names a specific sibling tool.

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?

'Use it to catch up, not to wait' gives implied guidance and even a when-not, but the alternative it is contrasting with (presumably get_delegated_task_updates) is never named. An agent must infer which sibling corresponds to 'wait'.

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