get_task

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

Declares read-only behavior and describes return format (full task JSON including UDA fields and annotations). No annotations exist, so description carries full burden; it lacks error handling details but covers essential behavioral traits for a simple read operation.

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?

Three short paragraphs, each with a distinct purpose: purpose, return details, usage comparison. No redundant sentences. Efficiently structured.

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 the tool's simplicity (1 required param, no annotations, no output schema shown), the description fully covers what the agent needs to know: what it does, how to identify the task, and when to use it over alternatives.

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?

Single parameter 'uuid' has 0% schema description coverage. Description compensates by explaining why UUID is critical (local IDs change) and that it returns complete data. Adds meaningful context beyond schema type.

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?

Clearly states 'Get a single task by UUID and return all its fields.' Specifies verb (get), resource (task), and scope (by UUID, all fields). Distinguishes from sibling list_tasks by purpose.

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?

Explicit guidance: when to use this tool vs list_tasks ('Use this over list_tasks when you have the UUID and need complete field data'). Also warns about numerical IDs vs UUID, preventing misuse.

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