List Available Documents

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

Annotations provide readOnlyHint=true, so description need not repeat safety. Description adds that it lists only .docx files and uses a directory parameter, but does not disclose whether it recurses subdirectories, result format, or error behavior. Lacks return format details since no output schema.

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?

Single, well-structured sentence with no redundant words. Front-loaded with key information.

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 list tool, the description is adequate but lacks details on recursion, return value format, and explicit guidance on when to choose this over similar sibling tools. With no output schema, the agent may be uncertain about the response structure.

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%, so description must add meaning. It mentions 'specified directory' for the 'directory' parameter, but does not state that it is optional or defaults to current directory. Adds minimal value beyond parameter name.

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 action ('List'), resource ('.docx files'), and scope ('in the specified directory'). Distinguishes from siblings that operate on document contents or modify documents.

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?

Description implies use when needing to discover available .docx files before editing, but does not explicitly state when to use this tool versus listing tools like 'get_document_info' or 'get_document_text'. No when-not-to-use or alternatives mentioned.

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