prd_generate_section

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

No annotations are provided, so the description must carry the full burden. It states that the tool can 'generate or regenerate' sections, implying it may overwrite existing sections when a PRD ID is given. However, it does not explicitly disclose whether the operation is destructive, what permissions are needed, or any rate limits. The description is adequate but not thorough.

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 sentences, with the first sentence stating the core purpose and the second providing a usage scenario. It is front-loaded and contains no unnecessary words or repetition.

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 5 parameters, no output schema, and no annotations, the description covers the basic purpose and when to use. However, it does not mention what the tool returns (e.g., the generated section text) or the behavior when no prd_id is provided. It is adequate but could provide more detail for full completeness.

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%, so baseline is 3. The description adds contextual meaning beyond the schema: it clarifies that 'description' and 'product_name' are required if no prd_id is provided, and explains that prd_id provides context of the full PRD. This adds value over the raw 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 clearly states that the tool generates or regenerates a single section of a PRD. It specifies the resource (PRD section) and the action (generate/regenerate), and distinguishes itself from the sibling tool 'prd_generate' which likely handles full document generation.

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 provides clear context on when to use this tool: for iterative refinement of specific sections like 'Technical Architecture' or 'User Stories' without regenerating the entire document. It implies that for full document generation, one should use the sibling tool, though it does not name the alternative explicitly.

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