engain_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 mentions fetching a task and optionally refreshing metrics, but does not disclose read-only nature, authentication needs, or error behavior. The description is insufficient for a complete behavioral understanding.

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 two short sentences with no unnecessary words. It is front-loaded and easy to parse.

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?

Despite low complexity, the description does not mention the return value (the task object) or error conditions. Since no output schema exists, this information is missing. It also does not differentiate from sibling tools or provide context about when to use this tool versus others.

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 has no descriptions for parameters (0% coverage). The description adds meaning to refreshMetrics by stating it 'pull[s] live upvote/reply counts', which clarifies its purpose. taskId is self-explanatory from the tool name.

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 precisely states 'Get a single task by ID', which clearly identifies the verb and resource. It also mentions the optional refreshMetrics parameter. This distinguishes it from sibling tools like engain_get_tasks_bulk (multiple tasks) and engain_list_tasks (listing).

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 retrieving a single task by ID, and suggests setting refreshMetrics for live counts. However, it lacks explicit when-not guidance or alternatives, such as noting that engain_get_tasks_bulk should be used for multiple tasks.

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