icp_interview_synthesizer

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 only says 'extract', which implies a read operation, but it doesn't disclose whether the tool is read-only, what the output format is, or any side effects. This is a significant gap for a synthesis tool.

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 a single, front-loaded sentence with zero wasted words. It communicates the core function and input type immediately.

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?

There is no output schema, so the description should hint at what the tool returns (e.g., the nature of extracted patterns). It also doesn't mention any prerequisites or limitations. This leaves an agent unsure about the expected output and potential edge cases.

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 the baseline is 3. The description adds a small amount of value by clarifying that interview_notes and raw_transcripts are alternative input methods ('or'), but it doesn't elaborate on parameter semantics beyond what the schema already states.

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 a specific action (extract) on a specific resource (ICP patterns) from customer interview notes or transcripts. It's unambiguous and distinguishes this tool from scoring or deep-dive tools, though it doesn't name alternatives.

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 usage when you have interview notes or transcripts, but it doesn't explicitly compare to siblings like icp_deep_dive or icp_scoring_model, nor does it state when not to use this tool. The context is clear but not prescriptive.

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