收集需求信息

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

With no annotations, the description carries the full burden. It discloses that the tool returns a prompt rather than final output, and that it supports multi-round collection. However, it has a slight internal ambiguity between 'generates configuration' and 'returns a prompt', and it doesn't mention side effects or statelessness.

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 sentences, each providing distinct information: purpose, workflow, and multi-round capability. No redundant content, and the description is well-structured and front-loaded.

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 explains the tool's role in the workflow (gather -> configure) and the return type (prompt). The schema covers all parameters. It lacks an output schema, but the description is sufficient for a tool of this complexity within its context.

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% with all parameters described in the input schema. The description adds no additional parameter semantics beyond mentioning multi-round support, which is already implied by the sessionId and userResponse parameter descriptions. Baseline 3 applies.

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 collects user project requirements and generates structured question configuration. It explicitly mentions returning a prompt for AI to generate JSON and call the configure tool, which distinguishes it from sibling tools like configure, analyze, and build.

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 description implies this is the first step in a workflow where gather collects requirements, then configure is called for user input. It provides clear context for when to use gather (to collect requirements) but doesn't explicitly state exclusions or alternatives beyond the configure step.

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