ai_standard_init

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

The description discloses key behaviors: if project_slug is omitted, it lists projects and guides the user; if provided, it creates .acm/ and writes project.json. However, it does not mention side effects like network calls or user interaction details.

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 long, front-loaded with the main action, and contains no unnecessary words. It efficiently conveys both modes of operation.

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?

The description covers the main initialization workflow, but could mention next steps (e.g., using ai_cloud_pull/push) or prerequisites. Given no output schema, it is reasonably 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?

With 100% schema coverage, the description adds value by explaining the conditional behavior of project_slug. It also confirms defaults for workspace and force, enhancing understanding beyond 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 clearly states the tool's purpose: initializing a workspace with .acm/ directory and linking it to a StandarCloud project. It distinguishes between two modes based on whether project_slug is provided, which aligns well with the tool name and differentiates it from sibling tools like ai_cloud_pull/push.

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 provides clear context for when to use the tool (initialization), but lacks explicit guidance on when not to use it or alternatives. While sibling tools imply this is for setup, the description could mention subsequent sync tools.

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