sp_get_current_task

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

No annotations are provided, so the description carries the behavioral burden. The word 'Get' implies a read-only operation, and 'if any' correctly signals that an absence of an active task is a legitimate outcome. It does not describe error or none-return format, but there are no side effects obvious for this zero-parameter getter.

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?

One tight, front-loaded sentence states the resource, the operation, the system context, and the nullable outcome. There is no filler or repetition of the tool name.

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 zero-parameter getter, this description is largely complete: an agent knows exactly what to call and what it gives. It would benefit from explicitly stating the return value when no task is active (e.g. 'null'/'empty'), but the phrase 'if any' already covers most of the ambiguity.

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 properties, so parameter coverage is trivially complete. The description validly needs to provide no parameter-level details. Baseline 4 for zero-parameter tools applies.

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 names a specific verb ('Get') and a specific resource: the currently active/running task in Super Productivity, with 'if any' signaling a possible absence. This clearly separates it from siblings like sp_get_task, sp_list_tasks, and sp_set_current_task.

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?

Usage is implied by the purpose: call this when you need the current running task. However, it does not explicitly say when not to use it or name alternatives like sp_get_task for a specific task or sp_list_tasks for all tasks.

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