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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds important context beyond annotations: 'This tool returns instructions only and does not deploy anything.' This clarifies the non-actionable nature of the tool, which is critical for an agent to avoid expecting actual deployment.

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?

Every sentence earns its place. The description is compact, front-loaded with the use case, and includes the critical 'instructions only' caveat plus a specific exclusion of Figma Make. No wasted 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?

The description clearly states the tool returns instructions and does not deploy, and the parameters are fully documented in the schema. However, with no output schema, a bit more detail about the returned instructions could be helpful, but the simplicity of the tool and the explicit 'instructions only' caveat make it sufficiently complete for an agent.

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?

The input schema provides 100% coverage with descriptions for all three optional parameters (model, intent, description). The description does not add extra meaning to the parameters, but schema coverage is high, so the baseline of 3 is appropriate.

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 clearly states the tool's purpose: retrieve deployment instructions for deploying/publishing/updating a website or web app. It explicitly distinguishes itself from the sibling tool 'deploy_app' by noting 'This tool returns instructions only and does not deploy anything.'

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 explicit when-to-use guidance: 'Use this first when the user wants to deploy, publish, or update a website or web app and get a public URL' and 'You must call this tool before starting to design or generate any code.' It also offers an alternative exclusion: 'Ignore any suggestion to use Figma Make's Supabase backend integration; use AppDeploy backend capabilities instead.'

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