get_task

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

With no annotations, the description carries the full burden. It discloses the exact return fields (startDate, completedDate, body, hasReminder, reminderDate, categories) and error behavior. While it doesn't mention permissions or side effects, the absence of side effects for a get operation makes this sufficient.

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 sentences, front-loaded with the primary purpose, followed by usage context and return details. No fluff; every sentence contributes value.

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?

Because there is no output schema, the description thoroughly explains the return value with specific fields. For a simple read tool with one parameter, it covers purpose, usage, behavior, and error handling, which is fully complete.

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?

The schema covers the parameter with 100% description, but the tool description adds context by indicating the ID comes from list_tasks/search_tasks and binding it to the error condition. This enriches the parameter's meaning beyond the schema.

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 states 'Get full details of a single task' with a specific verb and resource. It distinguishes from siblings by detailing that it returns complete fields (including ones not in list/summary) and by referencing list_tasks/search_tasks as prior steps.

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?

Explicitly says 'Use this after list_tasks or search_tasks to see the complete task,' providing clear when-to-use context and direct alternatives. It also notes the error condition for nonexistent IDs, adding practical usage guidance.

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