taiga_tasks_get

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

With no annotations, the description carries the transparency burden. 'Get' implies a read-only operation, adding basic safety context, but it omits details about error handling, authentication requirements, or response format. The minimal read-only implication justifies a mid-tier score.

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, front-loaded sentence with no filler or redundancy. It is appropriately sized for a simple get tool.

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?

For a basic get-by-ID operation with full schema coverage and no output schema, the description is largely complete. However, it does not explicitly describe the return value, though this is arguably implicit for a get operation.

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 fully describes the single 'id' parameter with 100% coverage ('Task ID'), so the description does not need to add parameter semantics. It adds no information beyond what the schema already provides.

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 uses the specific verb 'Get' with the resource 'task' and identifier 'ID', making it clear this is a fetch operation. It distinguishes from sibling tools like taiga_tasks_list (list) and taiga_tasks_get_by_ref (by ref) through the explicit use of 'by ID'.

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 provides no guidance on when to use this vs. alternatives such as taiga_tasks_get_by_ref or taiga_tasks_list. It simply states the action without contextual exclusions or alternative recommendations.

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