set_borders

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

No annotations are provided, so the description describes parameter behavior well (edges options, style types). However, it does not disclose whether existing borders are overwritten or if there are any side effects, which limits transparency.

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 two sentences: the first conveys the main purpose, and the second efficiently details parameter options. No extraneous information.

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?

Given the tool's simplicity and lack of output schema, the description covers the primary parameters but omits behavioral details like overwriting behavior and the role of color. It is adequate but not fully comprehensive.

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?

With 0% schema description coverage, the description adds meaningful details for edges and style (e.g., 'all', 'outline', individual directions; style options). It does not explain color or session_id, but the key parameters are well-covered.

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 'Draw borders on a range.' It specifies the verb and resource, distinguishing it from sibling formatting tools like set_fill_color and set_font.

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 explains the possible values for edges and style, including defaults. While it doesn't explicitly state when to use vs. alternatives, the parameter descriptions imply usage for adding borders, and the context is clear.

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