office_word

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

No annotations provided. Description adds pricing and API endpoint but no behavioral details (e.g., what happens to the file, permissions, side effects). Minimal transparency beyond cost.

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?

Very short but lacks structure. The single line plus API link is concise, but the omission of a clear action makes it under-specified rather than efficiently informative.

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 no output schema and no description of return values, the tool is incomplete for an agent. The agent cannot know what to expect from the call, especially given the sibling tools that cover various document operations.

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 coverage is 100% with one parameter described as 'Word文件URL'. The description adds no extra meaning beyond the schema, so baseline 3 is appropriate.

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 says 'Word处理' (Word processing), which is vague and tautological. It does not specify the actual operation (e.g., read, convert, edit). Fails to distinguish from sibling office tools like office_excel or office_pdf_parse.

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 alternatives. With many office-related siblings, the lack of usage context makes it hard for an agent to decide correctly.

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