keystone_new_guide

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

With no annotations, the description carries the full burden, and it does disclose the tier strictness cascade, which is important behavioral context. However, it does not disclose behaviors like overwriting existing files (related to `force`) or error conditions, so transparency is only 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?

The description is concise and efficient, with two sentences that deliver the essential information. It front-loads the purpose and then explains the tier system without excess.

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?

The description provides the core purpose and the important tier semantics, but it omits details about the `force` parameter and any behavioral notes about file creation. Given the simplicity of the tool, it is mostly complete, but the missing parameter explanation leaves a gap.

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 description adds meaning for the `tier` parameter, explaining the three allowed values and their hierarchy, which the schema does not do. However, `name` and `force` receive no explanation, leaving them to be inferred from their names alone.

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's function: scaffolding a new guide markdown file in a specific directory. The verb 'Scaffold' and the resource 'guide markdown file' make it distinct from sibling tools like keystone_new_script or keystone_new_sensor.

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?

It provides clear context that this tool is for creating guides, which differentiates it from other new tools. However, it does not explicitly state when not to use it or mention alternatives, leaving room for ambiguity in tool selection among siblings.

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