List TacticalRMM Tasks

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

The description reinforces the readOnlyHint by explicitly stating 'read-only' and adds the important behavioral detail that it 'does not run tasks,' which is not covered by annotations. The '/tasks/' source also provides endpoint context. No contradictions with annotations.

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 concise, consisting of two sentences, front-loaded with the main action, and contains no unnecessary words. It is well-structured for quick comprehension.

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?

The tool is a simple list operation with a well-documented schema and strong annotations. The description adequately covers the purpose and safety behavior, though it could mention the return format or explicitly differentiate from list_agent_tasks. Given the low complexity, it is sufficiently 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?

All three parameters (limit, offset, response_format) are fully described in the input schema with clear descriptions, so the description adds no additional parameter semantics. Baseline 3 is appropriate given 100% schema coverage.

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 uses the specific verb 'List' and identifies the resource as 'TacticalRMM automated tasks' with the source endpoint '/tasks/'. This clearly distinguishes it from siblings like list_agent_tasks, which are agent-scoped, and from task-execution tools.

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 states the tool is read-only and does not run tasks, giving context for safe use. However, it does not explicitly mention when to use this tool over alternatives such as tacticalrmm_list_agent_tasks, nor does it provide exclusions or prerequisites.

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