Assign lists to groups

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

No annotations are provided, so the description must carry the full behavioral burden. It reveals that the tool modifies group assignments and can clear them (set to null), implying mutable behavior. However, it does not mention side effects, required permissions, or whether the operation is idempotent. The description adds value beyond the schema but has 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 concise at two sentences, front-loading the main purpose. The first sentence covers the primary use, and the second sentence adds minor details about sub-uses and parameter types. Every sentence adds value, though it could be slightly more compact without losing clarity.

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?

Given there are no annotations, no output schema, and only one parameter with nested objects, the description covers the tool's core behavior but lacks information on return values or what happens on failure. The context is adequate for a simple assignment tool, but a bit more could help the agent understand the response or error cases.

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%, so the description must compensate. It explains that 'list' can be a name or listId, and 'group' can be a group name or null to clear, adding meaning beyond the schema's types. This clarifies the parameter semantics effectively.

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 clearly states the verb 'Assign' and the resource 'Microsoft To Do lists to named groups/folders', and distinguishes this tool from siblings like todo_get_lists by explaining the purpose is to organize lists into groups for later retrieval. It also mentions sub-uses like moving or clearing assignments.

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 explicit use cases (assign lists to groups, move a list to a different group, clear a group) but does not specify when not to use this tool versus alternatives such as creating a list or login. No sibling is directly excluded, but the use cases are clear.

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