SousChef

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

No annotations are provided, so the description carries full burden. It mentions conversion behavior and return format but lacks critical behavioral details: whether this is a read-only analysis or creates files, what permissions are needed, how errors are handled, or any rate limits. The description is insufficient for a mutation/conversion tool with zero annotation coverage.

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 well-structured with clear sections (purpose, Args, Returns) and uses bullet-like formatting. It's appropriately sized with no wasted sentences, though the formatting could be slightly more polished for optimal front-loading.

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's complexity (conversion between different infrastructure-as-code systems), the description covers purpose, parameters, and return value. With an output schema present, it doesn't need to explain return values in detail. However, it lacks behavioral context about the conversion process (e.g., assumptions, limitations, error handling).

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 0% schema description coverage, the description compensates well by explaining all three parameters in the Args section: 'deployment_recipe_path' (path to Chef recipe), 'deployment_pattern' (Chef patterns with enum values), and 'target_strategy' (Ansible strategies with enum values). This adds significant meaning beyond the bare 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 specific action ('Convert Chef application deployment recipe to Ansible deployment strategy') with precise resources (Chef deployment recipe, Ansible strategy). It distinguishes from sibling tools like 'generate_playbook_from_recipe' by focusing specifically on deployment strategy conversion rather than general recipe-to-playbook generation.

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 implies usage context through parameter descriptions (e.g., 'deployment_pattern' options) but doesn't explicitly state when to use this tool versus alternatives like 'generate_blue_green_deployment_playbook' or 'generate_canary_deployment_strategy'. No explicit exclusions or prerequisites are mentioned.

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