promote_list_item

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

The description discloses the exact effect (decrease ilvl by 1, min 0), the return value ({para_id, ilvl}), and the error condition. No annotations are provided, so the description carries the full burden; it is clear but could mention side effects like impact on numbering.

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 extremely concise: two sentences that cover purpose, behavior, and error handling without any superfluous text.

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 the tool's simplicity (one parameter, clear effect, and output schema mentioned), the description is reasonably complete. It covers what, how, and error cases. It could optionally reference how to obtain the para_id but is not strictly necessary.

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?

The schema has 0% description coverage, and the tool description does not explain the 'para_id' parameter beyond its name. The description should clarify that para_id is the paragraph ID of the list item to promote, but this is missing.

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 specifies the exact action: 'decrease the list indentation level (ilvl) of a paragraph by 1, minimum 0.' It clearly distinguishes from the sibling tool 'demote_list_item' which does 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 mentions that a ValueError is raised if the paragraph is not a list item, which implies the prerequisite. However, it does not explicitly contrast with other list tools or provide guidance on when to use this versus alternatives.

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