Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with each parameter having a brief description in the schema (e.g., 'Body name' for source_body_name and new_body_name, 'xy|xz|yz' for plane). The tool description adds no additional meaning. Since the schema already provides basic parameter info, a baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.