docx_list_sections

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

The description correctly labels the tool as 'Read-only', which is the primary behavioral trait. No annotations are provided, so the description carries the full burden; it does not mention error handling or output format, but for a simple read operation it is adequate.

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 extremely concise—two fragments totaling 11 words—with no redundancy. It front-loads the key behavioral trait 'Read-only'.

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?

While the description lists what properties are inspected, it does not specify the return structure (e.g., list of sections). For a list tool with no output schema, the description should clarify the output format.

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 explanation in the description or schema (0% coverage). The description does not clarify expected path format or constraints, providing minimal added value 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 inspects section properties, margins, page size, and header/footer refs, which aligns with the tool name 'list_sections'. It distinguishes itself from siblings like 'docx_list_parts' by specifying the resource (sections).

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_inspect' or 'docx_list_parts'. The description only states what it does, not the context of use.

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