create_heu_document

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

With no annotations provided, the description carries the full burden. It discloses creation, sharing, and email sending, and asks for confirmation. However, it lacks details on side effects (e.g., whether the template is modified), authentication requirements, rate limits, or idempotency. The side effects are stated but insufficiently deep.

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 three sentences, each earning its place: first defines core action, second adds email detail, third provides critical usage instruction. It is front-loaded with the main action and contains no fluff.

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 7 parameters, a nested object, and no output schema, the description is incomplete. It does not explain what HEU documents are, what the return value is, or error conditions. The confirmation instruction is good, but overall context is insufficient for a tool of this complexity.

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?

The input schema has 100% coverage, so parameters are already described. The description adds no new semantic information beyond what is in the schema; it merely mentions 'existing template' and 'email' which align with existing parameter descriptions. Baseline 3 is appropriate.

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 tool creates and shares a new HEU document from an existing template and sends email. It distinguishes itself from siblings like create_pdf_document by specifying the HEU document type and the template-based creation process.

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 includes an instruction to ask for user confirmation before executing, which is a usage guideline. However, it does not explicitly state when to use this tool versus alternatives like create_pdf_document or when not to use it.

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