get_task

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

With no annotations and no output schema, the description carries the full behavioral burden, yet it only says 'detailed information' without stating what fields are returned, whether permissions are required, or how an invalid/missing ID behaves. The safety and response profile is left entirely opaque.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity is partly the cause of the missing detail rather than a deliberate compression of rich content.

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 lookup tool with zero annotations, no output schema, and two undocumented parameters, the description leaves an agent guessing about return contents, error handling, and the meaning of includePosition. Not adequate to call the tool correctly without opening the schema.

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 only 33%: board_name is documented (with a useful pointer to list_boards) but task_id and includePosition have no description anywhere. The description mentions the ID lookup but never explains the format of task_id or what includePosition toggles, so it fails to compensate for the coverage gap.

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 and resource ('Get detailed information about a specific task') and the access key ('by its ID'), which distinguishes it from sibling collection getters like get_all_tasks and get_tasks_by_column. It does not explicitly name any sibling, so differentiation is only implicit.

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?

'by its ID' implies the precondition that a task ID is already known, which is the only usage signal. There is no statement of when to prefer this over get_all_tasks, get_tasks_by_column, or get_subtasks, and no exclusions.

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