docx_list_images

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

With no annotations, the description must carry transparency burden. It states 'Read-only.' indicating no document modification, but lacks details on output format, performance, or any other behavioral traits. Minimal disclosure.

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?

Extremely concise (8 words) and front-loaded with 'Read-only.' Every word serves purpose, but could be slightly expanded to improve completeness without sacrificing brevity.

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 no output schema and simple parameter, description is insufficient. It fails to describe the exact output (relationship IDs, alt metadata format) or any usage context. Leaves gaps for practical use.

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?

Single parameter docx_path has 0% schema description coverage. Description adds no meaning beyond the parameter name and type. Does not clarify expected format or constraints.

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?

Description clearly states it lists drawing/pict objects (images) and returns relationship IDs and alt metadata. Verb 'list' on resource 'images' is specific and distinguishes from siblings like docx_list_parts or docx_list_paragraphs.

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 other listing tools (e.g., docx_list_paragraphs, docx_list_content_controls). The 'Read-only' prefix hints at safety but doesn't help select among many sibling tools.

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