apply_drawing_style

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

Without annotations, the description carries the full burden for behavioral disclosure. It indicates mutation ('creates or updates') but omits details on side effects (e.g., overwriting existing layers), required permissions, or the return value (though output schema exists but is not described). The term 'audited' implies validation but is not explicit.

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 a single sentence with no unnecessary words. It efficiently conveys the core purpose. However, for a tool with an output schema and no parameter descriptions, slightly more elaboration would be beneficial.

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?

Although the tool has an output schema (not described), the description lacks behavioral context for a mutation tool. It does not mention return format, error conditions, or the lifecycle of the audited recipe. Given one parameter with no description, the description is incomplete.

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 0%, so the description must compensate. However, the description does not mention the parameter 'recipe_id' at all, leaving its purpose and allowed values completely unexplained. The schema provides a default but no further guidance.

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 'creates or updates' Rhino layer hierarchy, plot weights, colours, and linetypes, and specifies that it uses an 'audited drawing recipe'. This is a specific verb+resource combination that distinguishes it from sibling tools like get_drawing_recipe or list_drawing_recipes.

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. There is no mention of prerequisites (e.g., recipe must exist), nor any conditions under which other tools like execute_rhino_script or create_design_scene would be more appropriate.

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