restart_numbering

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

No annotations are provided, so the description carries full burden. It only mentions adding lvlOverride with startOverride, but does not disclose side effects, required permissions, error conditions, or whether changes are permanent. This is insufficient for safe tool invocation.

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, 11 words, front-loaded with key action. However, it could be more informative without sacrificing conciseness. Still, it earns its space.

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?

The tool has low complexity (3 params, 1 required, has output schema) but the description lacks usage context, prerequisites, and error handling. It is minimally complete but leaves several gaps.

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 description coverage is 0%, so description must compensate. It mentions 'paragraph' and 'startOverride' but does not explain the three parameters (para_id, level, start) or their roles. The agent cannot infer that level is the list level and start is the starting number from the description alone.

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 specific verb 'restart list numbering' and the resource 'at a paragraph', with a technical detail about what it adds. This distinguishes it from siblings like suppress_numbering or create_multilevel_list.

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 explicit guidance on when to use this tool vs alternatives like suppress_numbering, or prerequisites such as requiring an existing list. The description does not mention any exclusions or context.

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