get_sales_blueprint

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

Annotations indicate read-only and open-world hints, but the description adds valuable behavioral context: it's a comprehensive generator tool that creates multiple artifacts (not just a single document). The description doesn't contradict annotations and provides insight into the scope and output nature beyond what annotations convey.

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, well-structured sentence that efficiently communicates the tool's comprehensive output. Every word contributes to understanding the tool's purpose without redundancy or unnecessary elaboration.

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?

For a generative tool with read-only/open-world annotations but no output schema, the description adequately conveys what will be produced. However, it doesn't specify format (e.g., document type, structure) or whether outputs are editable/templates, leaving some implementation details unclear.

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?

With 100% schema description coverage, the schema already documents all 5 parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema descriptions, so it meets the baseline expectation without providing extra semantic value.

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 specific action ('Builds everything you need') and the comprehensive output (job description, comp structure, interview questions, ramp plan, activity targets). It distinguishes itself from siblings by focusing on sales hiring infrastructure rather than prospecting, classification, or other sales-related functions.

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 context ('to make your first sales hire') but doesn't explicitly state when to use this tool versus alternatives. No guidance is provided about prerequisites, timing, or comparison to other tools like 'get_icp_profile' or 'simulate_buyer_persona' that might be related to sales planning.

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