Gerar scaffold de UI

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

With no annotations, the description carries full burden for behavioral disclosure. It mentions 'sobrescreve' (overwrites) but gives no detail on what gets overwritten, side effects, or safety. It also omits the 'dashboard' variant that appears in the schema, which could mislead.

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 a single, efficient sentence with no fluff, front-loading the main action. However, it is so brief that it sacrifices essential information, making it minimally adequate in structure.

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?

Given the tool has 7 parameters, no output schema, and no annotations, the description is too sparse. It fails to explain the variants, overwrite behavior, or use cases, leaving the agent without enough context to use the tool correctly.

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 description coverage is 0%, so the description must compensate by explaining parameters. It only vaguely refers to 'variantes' without connecting to uiVariant, and ignores resourceDir, overwrite, uiPage, htmlDir, uiTheme, and title. No added meaning beyond the 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?

The description uses a specific verb 'Gera ou sobrescreve' (generates or overwrites) and identifies the resource 'bundle de UI' with variants, clearly stating the tool's function. It distinguishes from siblings like fivem.ui_add by focusing on whole-bundle generation/overwrite rather than adding a single page.

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?

No explicit guidance on when to use this tool versus alternatives like fivem.ui_add or fivem.resource_create. The description implies usage for scaffolding UI bundles but does not state when this is preferred over other tools or any exclusions.

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