update-sections

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

The description repeats the annotation's destructive nature ('Update') but adds no additional context about side effects, error handling, or the behavior when a section ID doesn't exist. Annotations already indicate destructiveHint=true, so the description contributes little.

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?

A single, front-loaded sentence that directly conveys the tool's purpose with no extraneous words. Every word earns its place.

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?

While the tool is simple and has an output schema, the description omits usage context, such as what happens on success or failure. The destructiveHint annotation is present, but the description doesn't elaborate on prerequisites or postconditions.

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 100%, and the schema already documents the 'sections' parameter and its nested fields (id, name, description). The description adds no extra meaning beyond what the schema provides, justifying the baseline score.

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 the action ('Update') and the resource ('existing sections'). It specifies multiple sections, distinguishing it from single-section operations. However, it does not explicitly list the updatable fields (name, description), relying on the schema.

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 guidance on when to use this tool versus alternatives like 'add-sections' or 'update-tasks'. No prerequisites, exclusions, or context about when updates are appropriate. Sibling tools are not mentioned.

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