create_multilevel_list

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

With no annotations, the description carries full burden but only states 'Create a multilevel list in numbering.xml' and gives a dict format. It does not disclose side effects, whether it modifies existing numbered lists, or any permissions needed, which is insufficient for a creation tool.

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 short and direct, with one sentence and a dict format. It is front-loaded but could be slightly more structured; still, it avoids unnecessary words.

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?

Despite having an output schema (not shown), the description doesn't mention return behavior or how the created list relates to the document. The tool's complexity (multilevel list creation) demands more context about integration with other list features.

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, so the description must compensate. It lists the expected keys for each level dict (num_fmt, lvl_text, indent, hanging, style?), adding meaning beyond the schema's generic 'additionalProperties: true' array. However, it omits details on parameter types or constraints.

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 'Create a multilevel list in numbering.xml', specifying a specific verb and resource, and distinguishes from sibling tools like add_list which likely adds a list instance to the document content.

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 provides no guidance on when to use this tool versus alternatives such as add_list or other list manipulation tools, leaving the agent without decision context.

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