jekyll_scss_create

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

With no annotations, the description carries the full burden. It does disclose the key traits: it mutates project files, writes into the configured SCSS tree, and supports a dry_run preview, plus that a stub is generated when content is omitted. It omits overwrite/collision behavior, permission requirements, and error semantics for an existing partial.

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?

Four short front-loaded sentences with no filler; the purpose leads and the write-location and dry_run facts follow. Slight redundancy between 'Writes under the configured SCSS tree' and 'Modifies project files' keeps it from a 5.

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?

For a mutation tool with no annotations and no output schema, the description covers destination and dry_run but leaves overwrite behavior, validation failures, and required permissions unstated. Adequate but with clear gaps.

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 75% and the schema already documents name, content, and category. The description only adds that dry_run is supported, without explaining its effect; the remaining parameter meaning lives in the schema. Baseline 3 is appropriate.

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?

Specific verb (Create) + resource (new SCSS partial), with clarifying examples and the write location ('under the configured SCSS tree'). An agent can distinguish this from jekyll_scss_list and jekyll_scss_get without opening a schema.

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 when-to-use or when-not-to-use guidance and no alternatives named. 'Supports dry_run' hints at a preview workflow but never says when to prefer dry_run or what happens if the partial already exists.

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