readOfficeDoc

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'converted from PDF' which adds some context, but it does not state whether the operation is read-only, has side effects, or any limitations such as content truncation or format fidelity. The description lacks essential behavioral transparency.

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, compact sentence that front-loads the core action. It contains no redundant information and earns its place with the specific detail about PDF conversion.

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?

For a simple tool with one parameter and no output schema, the description covers the basic purpose and return format ('as text'). However, it lacks context on when to use the tool, and the PDF conversion detail raises questions about input format and output fidelity without clarification. It is minimally complete but has clear gaps.

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 already provides a description for docId ('ID of the Office document to read') with 100% coverage. The tool description adds no new parameter-specific semantics beyond what the schema gives, so a baseline score of 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?

The description clearly states the tool retrieves content from a specific Office document as text, with a specific verb and resource. It distinguishes itself from sibling tools like listOfficeDocs and searchOfficeDocs by focusing on a specific document's content, and from readGoogleDoc by explicitly targeting Office documents.

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 provides no explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., obtaining a docId from listOfficeDocs) or exclusions. The usage is only implied through the phrase 'specific Office document', which is insufficient for clear decision-making.

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