Git Fetch (host-side)

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

無 annotations 提供，描述承擔全部責任。描述清楚揭露這是唯讀網路操作、不會動工作目錄、且在 host 端執行。雖未說明授權需求或失敗行為細節，但對這個工具而言已屬充分，僅略遜於完整揭露。

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?

描述僅兩三句，前段即點出核心用途與唯讀性質，後段補充典型場景與排除項。雖略長但資訊密度高，無冗餘內容，只是可再更精簡。

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?

無 output schema、無 annotations，但描述已涵蓋目的、使用情境、不做之事、remote 名稱限制。雖未說明返回格式或錯誤處理，但對一個 fetch 工具而言，該提供的上下文已足夠。

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 為 100%，所有 5 個參數皆有 schema 內描述。描述本身未再補充參數細節，但說明了 remote 只接受名稱不接受 URL 的約束（此點 schema 也有）。依據高覆蓋率基準，給 3 分合理。

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?

清楚說明在主機端對本機 repo 執行 git fetch（唯讀網路操作），並明確指出不動工作目錄。區分了與 sandbox 內 git fetch 的差異，且與其他 sibling（如 az_git_ls_remote、az_devops）有別。

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?

明確說明典型使用情境（Cowork sandbox 內 git fetch 被 proxy 擋 403 時），並說明完成後的效果。也主動排除 push/pull 等寫入操作，提供清晰的 when-to-use 及 when-not-to-use 指引。

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