preview_deploy

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

Beyond the annotations, the description discloses that the token is single-use and valid for only 5 minutes, and that the preview must be shown to the user first. This is useful behavioral context and does not contradict the readOnly or destructive hints.

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 short sentences with the core outcome front-loaded and the user-facing instruction included with no filler. Every sentence earns its place.

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?

The tool is simple, has an output schema, and the description covers the preview/token workflow well. However, the complete lack of guidance on the 'domain' parameter leaves a real gap for an agent preparing the call, making the description barely adequate.

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%, and the description never mentions the sole 'domain' parameter, its accepted values, or how it is used. The description adds no meaning beyond the parameter name and type constraints.

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 ('Calcula') and names a concrete resource ('prévia e token de uso único') with a clear validity constraint. This distinguishes it from deploy_site and other siblings by framing it as the preview/token-generation step.

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 instruction 'Mostre a prévia ao usuário antes de enviar' implies a pre-deploy workflow, but it never explicitly states when to choose this tool over siblings like deploy_site, nor does it provide exclusions. The usage is implied rather than fully specified.

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