docx_list_bookmarks

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

Behavioral transparency is minimal. The description notes it is read-only, but fails to disclose what happens if the file is missing, if no bookmarks exist, or any side effects. Annotations are absent, so the description should compensate.

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 very short (one sentence) and front-loaded with 'Read-only', which is good. However, it could be more informative without sacrificing 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?

For a simple tool with one parameter and no output schema, the description is somewhat complete in stating the purpose. However, it lacks details about return value format, error conditions, or edge cases, which would be helpful.

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% and the description provides no details about the required 'docx_path' parameter, such as expected format or path resolution. The agent gets no help understanding parameter semantics.

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 'List', the resource 'bookmarks and paths', and the purpose 'for cross-reference preservation'. It distinguishes from siblings like docx_list_anchors since bookmarks are a specific feature.

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 guidance on when to use this tool versus alternatives such as docx_list_anchors or docx_list_headings. The description only says 'Read-only' but does not specify context or exclusions.

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