gangtise_drive_list

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

No annotations are provided, placing the full burden on the description. The description does not disclose behavioral traits such as read-only hint, permission requirements, rate limits, or pagination behavior (though schema hints at pagination with size and fetchAll). It lacks explicit behavioral context.

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 concise, consisting of a single sentence plus a necessary date/time context instruction. The instruction is front-loaded and relevant for the agent to interpret user queries correctly. It could be slightly tighter, but overall efficient.

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 the tool has 8 parameters and no output schema or annotations, the description covers the basic function and filter capabilities but omits details about pagination, the from parameter, and what the output contains. It is adequate but not fully comprehensive.

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?

With 75% schema description coverage, the schema already explains most parameters. The description adds a high-level overview of filter types (keyword, file type, space type, time range) but does not add significant new meaning beyond the schema. The from parameter is left undocumented in the description.

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 '查询 Gangtise 云盘文件列表' (query Gangtise drive file list) and mentions filtering capabilities, establishing a specific verb-resource relationship. However, it does not differentiate from sibling tools like gangtise_drive_download or other list tools, so it loses a point.

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 guidance on when to use this tool versus alternatives, nor does it specify prerequisites or exclusion criteria. It only describes what the tool does, leaving the agent without context for selection.

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