akai_recipe

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

The description gives minimal behavioral info: it produces a .bfrecipe file and is in the 'pipeline' category. No annotations exist, but the description does not disclose side effects, destructive nature, or authentication needs. This is insufficient for a tool with no annotations.

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 one sentence, highly concise and front-loaded with the tool name. However, it could include more useful information without being verbose.

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 the tool has no output schema and two optional parameters, the description should explain what 'args' and 'stdin' do in the context of a recipe registry. It only states the output file type and category, missing essential context for an agent to use it correctly.

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% (both 'args' and 'stdin' have descriptions), so baseline is 3. The description adds no additional meaning or context for how these parameters are used in recipe registry management.

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 states 'Recipe Registry Management' and 'Produces: .bfrecipe', but lacks a specific verb (e.g., create, execute, manage) and does not distinguish from sibling tools like 'akai_pipeline'. The purpose is vague and could apply to many operations.

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 provided on when to use this tool versus alternatives (e.g., other akai tools). There are no prerequisites, context, or exclusions mentioned.

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