init

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

Without annotations, the description carries full burden. It discloses that initialization creates files and directories, and that re-running without force returns status. However, it does not detail whether overwriting is destructive, permissions needed, or what 'current status' means exactly.

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?

Three sentences with no wasted words. First sentence states the purpose, second details artifacts, third covers re-invocation and force flag. Information is front-loaded.

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?

Given it is a simple setup tool with one parameter and no output schema, the description covers inputs, behavior, and idempotency. It could mention output format but is sufficient for an agent.

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 coverage is 100%, and description adds value by explaining the 'force' parameter: 'use force: true to overwrite'. This provides context beyond the schema's default value.

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 verb 'Initialize' and the resource 'aidflow' in the current project, listing specific artifacts created (.aidflow/ directory, config, guides, skills). This distinguishes it from siblings like 'guide' or 'plan' which are post-setup tools.

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?

Explicitly says 'Call this once when first using aidflow' and explains the behavior on re-initialization (returns current status unless force=true). This guides when to use and when to avoid, though it does not compare with alternatives.

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