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

With no annotations, the description carries full burden. It reveals key behaviors: parallel execution, 10-person limit, generation of Client Compass, and a critical instruction not to summarize the coaching output. This is substantial transparency, though it could note side effects or permission requirements.

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 plus an important note, efficiently conveying purpose, use case, and output instructions. It is front-loaded and every part is useful, though it could be slightly more concise.

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 no output schema, the description thoroughly explains return expectations: 'Return the full Start Here coaching for each person (ask_them, know_this, avoid_this) — do not summarize or create tables.' It also covers input limits and the parallel nature. This is highly complete for a batch creation tool.

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 'a name is enough' but no additional detail beyond what the schema provides (object structure, required fields, max items). It does not enhance parameter semantics significantly.

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 what the tool does: 'Create up to 10 people (clients) in parallel and generate a Client Compass for each.' This provides a specific verb, resource, and scope, distinguishing it from sibling tools like create_person (single) and generate_compass (single client).

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 explicitly recommends use 'for re-engaging dormant leads — a name is enough,' giving a clear context. It does not explicitly mention when not to use or name alternatives, but the context from sibling tools and the parallel nature implies its niche.

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