scaffold_roles

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

No annotations are provided, so the description carries the full burden. It discloses that the tool is offline and deterministic, lists inputs, and implies it generates code artifacts. It does not mention any side effects or destructive actions, which aligns with its nature.

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 two sentences, concise, and front-loaded with the key purpose. It lists inputs efficiently without redundancy.

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?

No output schema is provided, so the description should explain return values. It states the generated artifacts (migration, gate snippet, bootstrap) but lacks details on format or how they are returned. For a code generation tool, this is adequate but not fully explicit.

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 100%, so the baseline is 3. The description merely lists the inputs without adding new meaning beyond what the schema already provides (defaults, constraints, descriptions).

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 generates a role-table migration, a requireRole gate snippet, and a first-operator bootstrap for Run402 function role gates. It also notes it is offline and deterministic, distinguishing it from siblings that likely involve actual network or project interactions.

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?

The description mentions it is offline and deterministic, implying it can be used without a project context. However, it does not explicitly state when to use vs alternatives or provide exclusions. The specificity clarifies its use case.

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