discover_business_needs

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

Annotations already indicate readOnly and idempotent. The description adds behavioral context: the tool returns a question script, must be called first, and the user must ask questions sequentially. No contradictions with annotations.

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?

Description is front-loaded with 'REQUIRED FIRST STEP' and uses formatting for emphasis. Every sentence adds value, though slightly lengthy. Could be tightened slightly but remains effective.

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 simplicity (1 optional param, no output schema), the description is complete. It explains the purpose, usage sequence, behavioral guidelines, and consequences of skipping. 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 coverage is 100% and describes the optional businessHint parameter. The description adds meaning by explaining that the hint lets the tool tailor follow-up questions to the niche, beyond the schema's description.

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 returns a question script and is the required first step before calling generate_site. It specifies the verb (returns), resource (question script), and context (business needs discovery). It distinguishes from siblings by mandating this tool before generate_site.

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 'REQUIRED FIRST STEP' and 'ALWAYS call this tool first when a user asks to build/generate a website.' It provides when-not to skip: 'Skipping discovery produces minimal text-only sites.' Also instructs to ask questions one at a time.

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