set_document_language

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

Given no annotations, the description details the exact XML modification (w:rPr/w:lang in word/styles.xml), providing clear behavioral insight. However, it omits side effects, error conditions, or prerequisites.

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 concise with one core sentence followed by a clear docstring-style args/returns section. Every sentence is informative with no redundancy.

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 description covers purpose, behavioral detail, parameters, and return format. It misses some edge cases but is adequate for a straightforward tool. Works well with the output schema context.

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?

The input schema has 0% description coverage, but the description fully explains the parameter 'language_code' as a BCP-47 tag with examples, adding significant value beyond the schema's bare type definition.

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 verb-resource combo 'Set the default document language' and further specifies the exact XML path where the language is written, distinguishing it from run-level language setting tools like set_run_language.

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 versus alternatives such as set_run_language. The description implies it sets the overall document default, but does not explicitly state when to choose this over other language-related tools.

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