word_list_citations

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

With no annotations provided, the description carries the burden of disclosing behavior. It indicates a non-destructive 'list' operation and the phrase 'already present' clarifies that no modification occurs. However, it does not mention permissions, error handling, or return format, which are relevant for a file-operation tool.

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 a single, tightly worded sentence with no redundancy. Every word contributes to the meaning, making it exceptionally concise and well-structured.

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 an output schema exists (so return values are likely covered), the description lacks any guidance on when to use this tool versus the many sibling tools. For a simple one-parameter read operation, the information is mostly sufficient, but the absence of usage context or alternative references leaves a noticeable gap.

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 schema has 0% coverage for document_path, and the description only obliquely refers to 'a .docx' without explaining the path format or requirements. Although the parameter name is self-explanatory, the description adds minimal additional meaning beyond the schema's structural details.

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's function with a specific verb ('List'), a distinct resource ('Zotero citations'), and a scoping container ('in a .docx'). This unmistakably distinguishes it from siblings like word_insert_citation and word_remove_citation.

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 does not explicitly state when to use this tool over alternatives or mention any exclusions. However, the purpose is self-evident, so usage is implied rather than explicit, matching the 'implied usage' benchmark.

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