rm_list_assignment_subtasks

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, covering the safety profile. The description adds only the clarification that subtasks are 'checklist tasks' and discloses no further behavioral details such as pagination, ordering, or response scope.

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 sentence with no filler. The key action and resource are front-loaded, and every word adds meaning.

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?

An output schema exists, annotations cover the read-only safety profile, and the two required parameters are implied by the description. The only minor gap is the lack of mention of pagination or response shape, but for a simple list tool this is not a significant omission.

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?

With 0% schema description coverage, the description must compensate, and it does partially by tying both parameters together: subtasks belong to a project assignment, implying project_id and assignment_id identify that assignment. However, it does not explain the ID formats or how to obtain them, though the parameter names are reasonably self-explanatory.

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 ('List') and resource ('subtasks (checklist tasks)') scoped to a project assignment. It clearly differentiates this from the sibling tools rm_create_assignment_subtask and rm_delete_assignment_subtask.

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 context makes it obvious this is the read operation for assignment subtasks, and the sibling names reinforce that it is the listing counterpart to create/delete. However, it does not explicitly state when to use this tool versus alternatives or mention exclusions.

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