works_drives_list

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It lists the output fields but does not explicitly state that the operation is read-only, mention permission requirements, or explain how the optional 'user' parameter affects results. It also lacks details on response shape, pagination, or error behavior.

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 sentence, front-loaded with the verb and object, and uses a parenthetical to enumerate fields. There is no filler or redundancy, making it appropriately concise and well-structured.

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 tool has a minimal schema, no annotations, and no output schema, placing a high burden on the description. It covers the output fields but omits the meaning of the 'user' parameter, any filtering behavior, and contextual details that would help the agent invoke the tool correctly. This is incomplete for even a simple list 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?

The only parameter, 'user', is not mentioned anywhere in the description. With 0% schema description coverage, the description must compensate and explain this parameter, but it completely omits it. The parenthetical list refers to output fields, not input parameters, so no semantic value is added.

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 uses a specific verb 'List' paired with a clear resource 'shared drives', and enumerates the returned fields (id, name, accessibleRange, permissionType, masters). This clearly distinguishes it from siblings like works_drive_get (singular get) and works_files_list.

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 implies usage as the tool for listing shared drives, but it provides no explicit guidance on when to use it over alternatives, nor any exclusions. The name and verb alone make the intended use reasonably clear.

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