Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description carries the full burden for all seven parameters. It explains action, secret_name, key_values, from_dotenv/from_json, force, and env, including which parameters apply to 'create' and the shape of key_values.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.