build_section_evidence_pack_v1

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

Discloses that the output is reproducible and that rebuild option exists, but no mention of side effects, permissions, or whether it overwrites existing packs. Annotations are absent, so description carries burden but leaves gaps.

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?

Concise: a title, one-line purpose, followed by a clear list of arguments and return values. No unnecessary sentences.

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?

Covers the main purpose, parameters, and returns. Lacks examples, error cases, or prerequisites. Output schema exists but is not shown; description compensates with return fields.

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?

Despite 0% schema coverage, the description briefly explains each parameter (e.g., outline_id is outline ID, max_chunks is maximum chunk count), adding meaning beyond the schema's type and default values.

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 it generates a fixed and reproducible evidence pack for a specified section, distinguishing it from siblings like build_evidence_pack and build_community_evidence_pack by explicitly mentioning section.

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?

No guidance on when to use this tool versus alternatives such as build_community_evidence_pack or build_evidence_pack. The description only states what it does without contextual usage advice.

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