twake_drive_read

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

With no annotations, the description itself must indicate side effects; the verb 'Read' signals a non-destructive fetch limited to text files. It does not explain behavior on invalid IDs, non-text files, or what exact return format the caller should expect.

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?

A single sentence with no filler, front-loading the core operation. This is appropriately concise for a one-parameter tool.

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?

The definition is nearly complete for a simple read-by-ID operation and works well with the schema. The only slight gap is the lack of an explicit statement about return value shape, since no output schema is provided.

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%, so the schema already documents 'id' as File ID. The description repeats this without adding constraints, examples, or formatting details.

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?

States a specific verb ('read'), a specific resource ('text file from Twake Drive'), and the lookup key ('file ID'). This clearly distinguishes it from siblings like twake_drive_list and twake_drive_upload.

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 phrase 'by file ID' implies this tool is for direct content retrieval when an ID is already known. It does not explicitly state when not to use it or mention alternatives such as twake_drive_list for discovering files.

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