Get task

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

With no annotations, the description carries the full behavioral burden. It transparently indicates a read operation ('Returns') and single-task granularity, but it does not disclose not-found behavior, whether deleted/restored tasks are included, or any authorization requirements. Adequate but shallow.

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 sentence with the essential 'Returns a single task by id' front-loaded. The trailing 'from the running backlog API' is somewhat redundant with the tool namespace but not costly. Overall compact and scannable.

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 simple one-parameter getter, the description plus schema is basically callable. However, with no annotations and no output schema, it omits useful context such as error handling, return shape, and read-only guarantees. It is adequate but not 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?

Schema description coverage is 0%, so the description must add meaning. Saying 'by id' clarifies that the integer task_id parameter is the task identifier, but it adds no extra detail beyond the schema's name and type. This is sufficient for a single, well-named parameter, but not rich.

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: 'Returns a single task by id.' This clearly distinguishes it from sibling list/find tools such as list_tasks and find_tasks_by_title, and from write operations like create_task or update_task. The core purpose is unambiguous.

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 id' implies this should be used when the agent already has a task_id, but the description does not explicitly contrast it with list_tasks or find_tasks_by_title, nor mention when not to use it. This is implied usage guidance rather than explicit routing.

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