format-excel-range-font

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

Annotations indicate readOnlyHint=false and destructiveHint=true, so it is a destructive write operation. The description adds no behavioral details beyond this, such as whether existing formatting is overwritten, whether confirmation is needed, or any permission requirements. With annotations present, the bar for additional disclosure is lower, but the description provides no extra context about the operation's effects.

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 extremely concise: a single sentence followed by a helpful tip. The main purpose is front-loaded, and the tip adds actionable detail without redundancy. There is no fluff, and every phrase contributes to understanding the tool's function.

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?

For a tool with a simple purpose and well-described parameters, the description is adequate. The annotations cover the destructive nature and confirm gate, and the schema covers the required parameters. However, it does not mention that formatting will overwrite existing font settings or specify any return values (though no output schema exists). It is complete enough for basic invocation but lacks a few nuanced details.

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 88%, so most parameters are already documented (e.g., name, size, color, underline enum). The description's tip simply lists the same properties (bold, italic, underline, size, color, font name) without offering additional meaning or examples beyond the schema. Since the schema does the heavy lifting, this score reflects that no extra value is added.

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 states a clear verb and resource: 'Format an Excel range font.' The tip adds the specific font properties that can be set (bold, italic, underline, size, color, font name). While it does not explicitly contrast with sibling tools like format-excel-range-border or format-excel-range-fill, the purpose is specific enough for an agent to distinguish it based on the font focus.

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 implies usage when font formatting is needed ('Set font formatting on a range'), which provides situational context. However, it does not mention alternatives or when not to use this tool, such as when dealing with borders or fills. The guidance is implied but not explicit, so it meets the baseline for implied usage.

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