pull_documents

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

With only readOnlyHint=false in annotations, the description carries most of the behavioral burden. It discloses useful details: local files that differ are kept, overwrite_local=true changes that, and uploads such as PDFs come down as bytes. This adds meaningful behavior beyond the annotation without contradicting it.

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 concise sentences with the primary action front-loaded. The second sentence adds essential nuance about bytes, kind, and overwrite behavior without unnecessary elaboration.

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 copy/download operation, the description covers destination, overwrite behavior, uploaded-file handling, and result metadata. There is no output schema and only minimal annotations, so some detail about the exact return structure is absent, but the tool remains understandable and callable.

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?

Schema description coverage is 0%, so the description must compensate. It clearly explains overwrite_local semantics and the meaning of the result rows' kind field. project_id and destination_directory are left self-evident from their names and the schema, which is acceptable given their intuitive roles.

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 begins with a specific verb and resource: 'Copy the project's documents and uploaded files into a local folder.' This clearly distinguishes pull_documents from sibling tools like push_documents or read_document, and the title is not needed to understand 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 makes the core use case obvious: copying project documents to a local folder. It gives context about uploaded files coming down as bytes and the kind field, but it does not explicitly name alternatives or say when not to use this tool versus siblings like push_documents.

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