drive_get_shared_drive

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

Annotations absent, so description carries full burden. It implies a read-only operation ('Get metadata'), but doesn't state side-effects, authentication needs, or rate limits. It's minimally transparent for a simple get tool.

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?

Single sentence with no wasted words. Front-loaded with verb and resource. Perfectly concise and 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?

No output schema provided, but description doesn't hint at what metadata is returned (e.g., name, description, permissions). For a simple tool, completness is lacking; agent may not know what to expect.

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?

Single parameter 'driveId' is already described in the schema (100% coverage). Description adds no extra meaning beyond the schema baseline.

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?

Description clearly states the action ('Get metadata') and the resource ('a shared drive in Google Drive'). It distinguishes well from sibling tools like drive_list_shared_drives (lists all) and drive_create_shared_drive (creates).

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?

No guidance on when to use this tool vs. alternatives (e.g., drive_file_info for files, or drive_list_shared_drives to get IDs). No prerequisites or context provided.

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