list_docs_in_folder

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only states that a formatted list is returned, but omits any information about permissions needed, behavior with empty folders, page_size handling, or whether the tool filters exclusively to native Google Docs vs. other file types. This lack of context leaves significant room for misestimation.

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 two sentences long, front-loads the primary action, and includes a return-type note. Every word earns its place, with no filler or redundancy.

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?

For a tool with three parameters (one required) and no comprehensive output schema visible, this description is insufficient. It lacks parameter semantics, behavioral caveats, and usage alternatives. The agent cannot confidently invoke this tool without guessing at the meaning of user_google_email and page_size, and the absence of any exclusion criteria makes it hard to distinguish from sibling listing tools.

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 schema description coverage is 0%, so the description must compensate by explaining the parameters. It fails to do so: it never mentions user_google_email, folder_id, or page_size, and only obliquely references a 'specific Drive folder.' Required parameters are left undefined, making successful invocation dependent on external knowledge.

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 verb 'Lists' and the resource 'Google Docs within a specific Drive folder,' which distinguishes it from siblings like list_drive_items (all files) and search_drive_files (search). The scope is explicit, making the tool's intent unambiguous.

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 list_drive_items or search_drive_files. It does not mention exclusions, prerequisites, or typical use cases beyond the basic action, leaving the agent to infer usage from the name and sibling context.

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