promote_list_item

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

With no annotations, the description carries full burden. It discloses the effect (decrease ilvl by 1, floor 0), the exact return value '{para_id, ilvl}', and an error condition ('ValueError if paragraph is not a list item'). However, it does not indicate whether the operation is reversible or idempotent.

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 concise sentences: first states the action and constraint, second covers returns and errors. No redundant information; 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 single-parameter mutation tool with an output schema (implied by the return description), the description is complete: it defines input, operation, output, and error condition. No missing behavioral details given the simplicity.

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% (no parameter descriptions), so the description must compensate. It mentions 'paragraph' in the context of para_id but does not explain that para_id is the identifier of the target paragraph. The parameter's purpose is inferable but not explicitly stated.

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?

Description clearly states the tool reduces list indentation level by 1 with a minimum of 0, using a specific verb ('Decrease') and resource ('list indentation level'). The name 'promote_list_item' contrasts with sibling 'demote_list_item', making the purpose unambiguous.

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 the tool is for promoting list items (reducing indent) but provides no explicit guidance on when to use it versus alternatives like 'demote_list_item' (which would increase indent). No exclusion or prerequisite conditions are mentioned, leaving context inferred.

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