drive_list_apps

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only states the action without describing read-only nature (implicit), potential side effects, authentication needs, or rate limits. The minimal text adds little beyond the name and title.

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 concise sentence that efficiently conveys the core purpose. While it could be expanded with more context, the structure is front-loaded and contains no fluff. It earns its place but misses opportunity for richer detail.

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 no output schema and no parameters, the description should at least hint at what information is returned (e.g., app names, IDs). The current text is adequate for a simple listing but does not fully describe the output or scope of 'installed apps', leaving the agent to infer.

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 input schema has zero parameters, so the description does not need to explain parameters. According to guidelines, baseline is 4 for 0-parameter tools. The description appropriately adds nothing beyond what the schema already covers (empty schema).

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 action ('List') and resource ('installed Google Drive apps'), making the purpose immediately understandable. However, it does not differentiate itself from sibling tools like 'drive_get_app' or 'drive_list', missing an opportunity to clarify when to use this specific listing operation.

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 such as 'drive_get_app' (to get a single app) or 'drive_search' (to find files). No context about prerequisites or typical use cases is given.

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