word_native_batch

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and non-idempotency, so the safety profile is covered. The description adds real behavioral context beyond that: operations run in an ordered sequence and the tool can drive either active or closed documents. However, it never says whether a failing operation aborts the batch or leaves partial edits, nor what 'overwrite' does on save.

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, purpose front-loaded, then a dense capability list. The list is long but each item earns its place by advertising an operation family the agent can request; no filler or restatement of the name.

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 destructive, 28-operation batch tool with no output schema and a deeply nested target object, the description covers the 'what' but omits execution failure semantics, whether results are returned per operation, and the caution implied by driving a user's live application window. Adequate but with clear 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 the description must compensate, and it does partially by naming capability areas (formatting, tables, styles, fields, bookmarks, headers/footers, protection, PDF export) that map onto the op constants. But it adds nothing about target.path vs active vs create vs visible, or about the character-offset semantics of start/end — the schema's structure carries most of the meaning.

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?

States a specific verb and resource ('Execute an ordered batch through real Microsoft Word') and enumerates the operation surface it covers, which lets an agent tell it apart from single-op siblings like word_append_paragraph or word_replace_text. It stops short of explicitly contrasting itself with those siblings, but the batch framing is unambiguous.

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?

Signals that this is the multi-operation path but gives no explicit when-to-use/when-not guidance and names no alternatives (e.g., use word_replace_text for a one-off substitution). The phrase 'Supports active or closed documents' hints at targeting modes but is not framed as guidance.

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