docx_get_outline

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

The description indicates the tool is read-only, which is a key behavioral trait. Without annotations, it adequately covers the safety profile, but lacks details on performance, permissions, or output format. For a simple read tool, this is acceptable but not thorough.

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 and to the point, with no filler. However, it sacrifices parameter clarity for brevity, missing an opportunity to add value in the single sentence.

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?

Given the lack of output schema and unclear parameter, the description is incomplete for an agent to use confidently. The tool's purpose is clear, but the agent cannot determine the required input format or the exact structure of the output.

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 single parameter docx_path has no description in the schema (0% coverage) and the tool description does not clarify its meaning, format, or constraints. An agent would not know how to specify the path correctly without additional context.

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 it is read-only and provides a heading outline with section paragraph ranges, specifically for large-document chunking. This distinguishes it from sibling tools like docx_outline or docx_list_headings, which likely do not include paragraph ranges.

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 for large-document chunking, but does not explicitly state when to use this tool vs alternatives like docx_outline or docx_list_headings. No exclusions or prerequisites are mentioned.

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