focus_get_task

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

No annotations are provided, so the description carries the full burden. It only says 'get', implying a read operation, but does not disclose the return format, authentication requirements, or behavior regarding optional parameters like include_assignees.

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 and front-loaded sentence. Every word earns its place, with no redundant 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?

With no output schema, no annotations, and four parameters (including an unexplained include_assignees), the description is too minimal. It does not describe the return value, parameter semantics, or default behaviors, leaving significant gaps.

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 descriptions cover 50% of parameters (workspace_id and organization_id), but the description adds only 'by ID' for task_id. It does not explain include_assignees, nor does it compensate for the lack of schema description on that parameter.

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 'get a task by ID' uses a specific verb and resource, clearly identifying the operation and its key parameter. It distinguishes this tool from siblings like focus_list_tasks and focus_get_project by focusing on retrieving a single task 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?

No guidance is provided on when to use this tool versus alternatives such as focus_list_tasks or focus_get_current_timer. There are no conditions, exclusions, or references to other tools for related use cases.

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