docx_list_anchors

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

With no annotations, the description bears full burden. It declares 'Read-only' which is good for safety, but lacks details about behavioral traits such as ordering, filtering, performance, or whether it includes all occurrences. The description is adequate but minimal.

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 a single sentence, very concise, and front-loaded with 'Read-only.' However, it is under-specified given the number of siblings and parameters. It could be expanded to include parameter details without losing conciseness.

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 tool has no output schema, 2 parameters with 0% coverage, and many sibling tools. The description fails to explain what a 'stable editing anchor' is, how max_preview affects the output, or what the return format looks like. Many gaps remain.

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, meaning the JSON schema does not describe any parameters. The tool description also does not explain what docx_path or max_preview mean. This fails to add meaning beyond the schema.

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 tool is read-only and lists stable editing anchors: content controls, headings, bookmarks, and paraId paragraphs. It distinguishes itself from sibling tools like docx_list_headings and docx_list_bookmarks by combining multiple anchor types into one.

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 the tool is for listing all stable anchors at once, but it does not explicitly state when to use this tool over more specific siblings like docx_list_headings or docx_list_bookmarks. No when-not or alternative guidance is provided.

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