yougile_get_task

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds context by enumerating the fields returned (title, description, assigned users, deadline, checklists, stickers, time tracking), which goes beyond the annotation. No behavior is hidden that would surprise the 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 a single, concise sentence that begins with the verb 'Get' and immediately identifies the resource and key fields. It contains no filler or redundant information, earning a perfect score for efficiency.

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 low complexity (one parameter, no output schema, annotations covering side effects), the description sufficiently explains what the tool does and what the response will contain. The field list provides enough detail for an agent to decide whether to invoke this tool.

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 input schema fully documents the sole parameter 'id' as a required Task UUID with 100% description coverage. The description does not add extra meaning beyond the schema, such as format constraints or examples, so the baseline score of 3 is appropriate.

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 states the tool retrieves full details of a task with specific fields listed (title, description, assigned users, deadline, checklists, stickers, time tracking), making the purpose of retrieving a single task clear. This distinguishes it from sibling tools like yougile_list_tasks, which lists tasks, and yougile_create_task/update_task, which modify tasks.

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?

The description implies usage when full task details are needed and a task ID is known. While it doesn't explicitly exclude alternatives or name sibling tools, the context is clear: use this tool to fetch a specific task rather than listing all tasks. No exclusions or prerequisites are stated, but the tool's purpose is self-evident.

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