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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds meaningful guardrail context beyond those hints: output is explicitly a draft, no Robert voice defaults are applied, and autonomous outbound is forbidden. These are the kinds of behavioral details an agent needs and do not repeat the annotations.

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 concise sentences with the primary action front-loaded and the safety constraints packaged into the second sentence. Every clause earns its place and there is no redundant restatement of the title or schema.

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 strong output schema, full parameter descriptions, and annotations covering safety and idempotency, the tool description covers the purpose, core inputs, and critical non-behaviors. Nothing essential to invoking the tool correctly is missing, and the schema handles the remaining return/delivery details.

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 description coverage is 100%, so the structured schema already documents all three parameters. The description adds light semantic framing by connecting prospect evidence, tenant voice profile, and PERSPECTIVE grounding to the processing pipeline, but it supplies no operational parameter detail beyond what the schema already provides.

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 names a concrete action ('Build a draft GrowthOS digital-clone render packet') and a specific resource, and the closing constraint ('No Robert voice defaults and no autonomous outbound') clearly separates it from any publishing or outbound sibling. It leaves no doubt that the tool produces a draft rather than taking external action.

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 intended use is implied: build a digital-clone draft from prospect, tenant profile, and perspective grounding. However, the description does not explicitly state when to choose this tool over sibling packet tools like growthos_opportunity_scout_packet or growthos_revenue_capture_packet, nor does it list exclusions or alternative conditions.

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