scaffold_provider

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

Despite no annotations, description explicitly states read-only, deterministic, idempotent, and explains no parameters and fixed endpoint. Fully discloses behavior.

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?

Three short paragraphs, each serving a clear purpose: what it returns, when to use, additional traits. Front-loaded with the main outcome. No unnecessary words.

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?

Fully covers all needed information for a zero-parameter tool: return format (plain text with code block), location (app/layout.tsx), dependency (scaffold_route_handler), and safety guarantees. No output schema needed.

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?

No parameters, so schema coverage is 100% by default. Description goes beyond by explaining why there are no parameters (endpoint path always /api/uploadkit from scaffold_route_handler), which adds value.

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 returns a ready-to-paste snippet for Next.js root layout with UploadKitProvider, which is a specific verb+resource. Distinguishes from sibling scaffold_route_handler by specifying it's the next step in wiring.

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 says 'When to use: right after scaffold_route_handler' and warns that without it, components throw at runtime. Provides clear context and alternative (scaffold_route_handler).

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