word_inspect_document

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

No annotations provided, so description bears responsibility. Describes behavior as inspecting and returning comprehensive statistics, but lacks details on side effects, permissions, or performance. Adequate but not exhaustive.

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?

Three sentences, each adding value: purpose, content, usage guidance. Front-loaded and no wasted words. Efficient structure.

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?

Given 3 parameters and existence of output schema, description covers purpose, usage guidance, and basic behavior. Could mention output schema structure or error handling, but still fairly complete for an inspection tool.

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 covers 100% of parameters with descriptions. Description does not add extra meaning beyond what schema provides, so baseline score of 3 applies.

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 verb 'inspect' and resource 'Word document elements', listing specific extractables (paragraphs, tables, images). Distinguishes from sibling tools by advising to use this before reading a specific part, making it a meta-inspection tool.

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?

Explicitly says 'Before deciding which part to read, please use this tool first', providing clear context when to use. Does not give negative examples but the guidance is distinct enough.

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