cg_create

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

No annotations; description only states scaffolding action and naming. Does not disclose side effects, authorization, or what gets created. Minimal behavioral context.

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 concise sentences, front-loaded purpose, no redundancy. Could be slightly more structured, but efficient.

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?

Lacks output specification and detailed behavior; adequate for a simple scaffold tool but misses side effects and return info. No output schema to compensate.

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 has 100% coverage but description adds value: explains name is a slug, domain/language are needed for widgets, and clarifies blueprint usage. Enhances schema with practical guidance.

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?

Description clearly states it scaffolds a widget or blueprint, explains naming convention, and distinguishes between the two via the is_blueprint parameter. It is specific and contrasts with sibling tools.

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?

Provides guidance on when to use name as slug and that domain/language are required for widgets but not blueprints. However, it does not clarify the difference from the sibling cg_blueprint tool.

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