create_multilevel_list

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

No behavioral details beyond creation location. Does not state if this operation is destructive, requires specific permissions, or interacts with existing numbering. Annotations absent, so description should compensate but fails.

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, no wasted words. Immediately states purpose and then specifies the level dict format. Efficient.

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?

Covers the level dict format adequately, but lacks context on the 'name' parameter, on prerequisites (document state), and on behavior for invalid inputs. Since output schema exists, return values need not be described, but other gaps remain.

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 description specifies the expected keys for each level dict in the 'levels' array, which helps agents understand the nested structure. However, the 'name' parameter is left completely undocumented. With 0% schema coverage, this partial info elevates it above baseline but still insufficient.

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?

Clearly states action and resource (multilevel list in numbering.xml). However, does not explain how this differs from 'add_list' or other list tools. The level dict format is provided, adding specificity.

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?

No usage guidance provided. An agent must infer from the name that this is for multilevel lists, but no comparison with sibling tools like 'add_list' or 'demote_list_item'.

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