word_create

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

Description claims content is provided, but input schema has no parameters. This contradiction misleads the agent about how to invoke the tool. No annotations to compensate.

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 sentence, no waste. However, brevity sacrifices necessary details, and the content claim is inaccurate.

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?

Lacks key details: location of created document, file naming, behavior on conflict, return value. No output schema or annotations. With no parameters, description should explain how to specify content.

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 has no parameters (100% coverage trivial). Description adds misleading 'given content' implying a parameter that doesn't exist. Actively harms understanding.

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?

Clearly states it creates a new Word .docx document with content, distinguishing from siblings like word_append.

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?

Implies use for creating new documents, but no explicit when-not or alternatives mentioned. Also, lack of content parameter undermines guidance.

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