uuid_generate

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

Details implementation (Node.js crypto.randomUUID for v4, spec-compliant for v7), confirms no network calls, and specifies output format (canonical xxxxxxxx-xxxx-Mxxx-Nxxx-xxxxxxxxxxxx). With no annotations, description fully covers behavioral traits.

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 sentences with logical flow: purpose, usage guidance, implementation details, output format. Every sentence adds value, no 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?

For a simple single-param tool with no output schema and no annotations, description covers all essential aspects: what it does, which version to pick, how it works internally, and what to expect. No 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 covers version parameter with enum and description. Description adds semantic distinction: v4 random vs v7 time-ordered with Unix-ms prefix for sorting. This enhances understanding beyond schema.

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 'Generate a single UUID' with specific versions (v4/v7). Verb 'generate' and noun 'UUID' are precise. Sibling tools are unrelated, so no differentiation needed.

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?

Explicitly advises when to use v4 vs v7: 'Use v4 for general-purpose; use v7 when UUIDs must sort chronologically.' Also notes no network calls, helping agents choose based on requirements.

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