pull_documents

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

The description discloses a non-obvious behavior: local files that differ are kept and not overwritten unless overwrite_local=true. This adds valuable context beyond the readOnlyHint=false annotation, though it does not cover other aspects like permissions or error handling.

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, front-loaded with the primary action, and includes only necessary behavioral detail. Every word earns its place.

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?

While the core action and overwrite behavior are covered, the description does not mention return values, preconditions (e.g., destination directory must exist), or error scenarios. Given the lack of an output schema, these omissions leave the tool's full behavior incompletely specified.

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 0% schema description coverage, the description compensates by explaining overwrite_local's effect. Project_id and destination_directory are only implicitly defined through the overall action, and the schema titles already make their roles clear. The description adds no further detail on formats or constraints.

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 'Copy' and resource 'project's documents' into a local folder, clearly distinguishing pull_documents from siblings like push_documents and read_document. It states the direction and scope of the 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 implies usage by stating the action, but does not explicitly mention when to use it over alternatives like read_document for single files or push_documents for the reverse operation. No exclusions or alternative tools are referenced.

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