pandaone_install_git

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds scope context ('project-internal', 'no global git') but does not disclose behavior such as download source, install location, or what probe_only returns. The description adds some value beyond annotations but not rich behavioral detail.

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 a single compact sentence with no filler. The parenthetical adds meaningful context without redundancy. 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?

For a simple tool with two optional, clearly documented parameters and non-destructive/idempotent annotations, the description plus schema is largely sufficient. The main gap is that there is no output schema and the description does not indicate what the tool returns, especially in probe_only mode.

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 100% — both probe_only and auto_download have clear descriptions. The main description does not add further parameter semantics, so the baseline score of 3 applies.

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 action ('安装便携版 git' / install portable git) and the resource (portable git). The parenthetical ('用于项目内 git hook，无需全局 git') adds context that ties it to project-internal hooks, but it does not explicitly differentiate from the sibling tool pandaone_install_hook, so it stops short of a 5.

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 gives a clear usage context: this is for project-internal git hooks and does not require global git. This tells the agent when the tool is appropriate, though it does not explicitly state exclusions or name alternative sibling tools.

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