demote_list_item

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

No annotations provided, so description carries full burden. It discloses the effect (increase ilvl by 1, max 8), return values, and error condition when paragraph is not a list item. However, it does not mention whether the operation is permanent or requires any permissions.

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?

Two sentences with no wasted words. The purpose and key details are front-loaded. Every sentence adds value.

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 simple tool with one parameter and an output schema, the description covers input, output, constraint (max 8), and error. It is mostly complete, though it could briefly explain 'ilvl' for clarity.

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 coverage is 0%, but the description provides minimal addition: it mentions 'paragraph' which hints that para_id refers to a paragraph ID. However, it does not explain how to obtain the para_id or any format, leaving the parameter ambiguous.

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 action: 'Increase the list indentation level... by 1, maximum 8'. It specifies the resource (a paragraph identified by para_id) and the result. It distinguishes from sibling 'promote_list_item' which would do the opposite.

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 implies usage on list items (raises ValueError otherwise) but provides no explicit guidance on when to use this tool vs alternatives like 'promote_list_item' or 'set_paragraph_indentation'. No when-not-to-use or context for selection.

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