Embed Zotero citation fields in a Word document

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the agent knows this mutates state and interacts with an external environment. The description adds valuable context beyond that: the exact marker syntax that will be replaced and the requirement to open the result in Word and refresh. It does not explicitly state whether the original docx is modified, but the schema's output_path describes a sibling output file.

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 front-loaded with the core action and follows with necessary marker examples. Every sentence earns its place: the marker list is essential for correct invocation, and the final refresh instruction is a required post-step. No filler is present.

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?

With a full output schema, 100% parameter description coverage, and annotations covering mutation and open-world behavior, the description is complete enough to invoke the tool correctly. It supplies the marker syntax and the Word refresh procedure, which are the key tool-specific details an agent needs. Nothing essential is missing.

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 100%, so the parameter semantics baseline is 3 even without description-level parameter detail. The description adds marker syntax relevant to the docx_path input, but it does not explain style, locale, output_path, or insert_bibliography beyond what the schema already documents.

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 states a specific verb and resource: replacing citation markers with Word fields the Zotero plugin can refresh. It names the marker syntax and the post-processing step, making its role clearly distinct from sibling tools like search_zotero or list_zotero_items. An agent can identify the tool without opening the schema.

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 by explaining the marker format and telling the user to refresh in Word afterward. However, it does not explicitly say when to use this tool versus alternatives or when not to use it. The intended context is inferable but not spelled out.

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