List sessions and tasks

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful scope by saying results are Muster-owned and include host capabilities. However, it does not describe ordering, pagination, or whether the list is exhaustive, leaving some behavioral gaps.

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 front-loaded sentence with no redundant phrasing. Every element, including the ownership scope and host-capability inclusion, adds useful information. There is no structural waste.

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?

This is a simple list tool with one optional enum parameter and annotations covering safety. The description states the resource and scope, but it omits parameter behavior, return-shape detail, and sibling-tool guidance. It is minimally adequate but has clear gaps for an agent deciding exactly how to call it.

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%, and the description never mentions the 'kind' parameter. It does not explain that 'kind' filters between sessions and tasks, nor what happens when it is omitted. The enum values are self-explanatory, but the description does not compensate for the missing schema documentation.

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 states a specific verb and resource: listing Muster-owned sessions and tasks. It also adds that host capabilities are included, which clarifies scope. It does not explicitly distinguish this tool from the sibling 'output', but the resource is clear enough to identify the operation.

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 gives no guidance on when to use this tool versus the sibling 'output', nor does it state any exclusions or prerequisites. Usage is only implied by the verb 'List'. An agent must infer the appropriate context without help from the description.

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