Initialize a project directory for Pandaone Guard by creating the .pandaone/ structure, config.json, and pandaone.jsonl files that enforce structured audit logging for AI code changes before commit.
在指定目录初始化 Pandaone AI Agent（创建 .pandaone/、config.json、pandaone.jsonl、可选 binary_snapshots.json）
| Name | Required | Description | Default |
|---|---|---|---|
| ext | No | 自定义受保护扩展名（如 ['.py', '.md']） | |
| root | Yes | 项目根目录路径 | . |
| no_binary | No | 禁用二进制 SHA256 快照保护 |
Changes observed during successful MCP inspections.
v0.7.14Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already signal that this is not read-only, not destructive, and not idempotent. The description adds value by enumerating what files get created, but it does not disclose behavior on repeated runs or whether existing files are preserved/overwritten, which matters given idempotentHint=false.
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?
One compact sentence conveys the core action and key artifacts with no filler. It is not broken into sections, but for a small tool that is acceptable.
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 3-parameter init tool with 100% schema coverage and annotations, the description is mostly sufficient, but it lacks details about rerun behavior, directory existence requirements, and outcome/output, especially with no output schema. It is adequate but not fully complete.
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%, so the onus on the description is low. The free-text adds little beyond the schema; 'optional binary_snapshots.json' roughly echoes the no_binary flag but is not mapped to parameters, and ext/root are left to the schema.
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 opens with a specific verb-resource pair ('initialize Pandaone AI Agent in specified directory') and lists the concrete artifacts it creates (.pandaone/, config.json, pandaone.jsonl, optional binary_snapshots.json). It is clearly distinguishable from siblings like pandaone_status or pandaone_log, though it does not explicitly contrast itself with other setup-like siblings (pandaone_install_hook, pandaone_install_git).
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?
No guidance is given on when to run init versus the sibling tools, nor when to toggle the optional features. The initialization purpose is implied by the name, but the description contains no explicit 'use when' or exclusion statements.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.