jekyll_scss_get

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

With no annotations present, the description carries the burden and does declare 'Read-only' plus the shape of what is returned (source plus parsed analysis). It omits failure behavior for missing/invalid paths and any size or performance caveats, which would round out the behavioral picture.

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?

Two sentences, zero filler, with the action and return contents front-loaded and the path constraint following. Every clause conveys distinct information.

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 single-parameter read tool with no output schema, the description adequately covers input semantics, read-only nature, and the returned payload. Only error/edge-case behavior on a nonexistent path is unaddressed.

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?

The schema already documents the single 'path' parameter at 100% coverage, so the baseline is 3. The description adds real meaning beyond the schema by specifying the path is relative to the project root and by naming the sibling tool that produces valid values.

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?

States a specific verb and resource ('Read an SCSS file') and enumerates exactly what the response contains (imports, variables, CSS custom properties, mixins, selectors). This clearly separates it from jekyll_scss_list (enumeration) and jekyll_scss_create (writing).

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?

Gives concrete invocation context: supply a path relative to the project root, and obtain that path from jekyll_scss_list, which routes the agent to the right sibling. It does not state when NOT to use it or what happens if the file is absent, so it stops short of full when/when-not guidance.

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