send_document

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

With no annotations, the description carries the full behavioral burden. It says the tool sends email, but does not disclose external side effects, permission requirements, whether sending is irreversible, rate limits, or what happens when emails are omitted.

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 front-loaded with the core action and then supplies only the necessary docType constraints. The list of supported types is long but directly useful, with no filler.

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?

It covers the key docType constraint well, but for an email-sending mutation with no annotations and no output schema, it leaves important gaps: whether emails are optional or default to something, what confirmation is returned, and what permissions or side effects apply are not explained.

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, but the description adds important semantic value by correcting the enum: it lists supported docTypes and states that purchase and purchaserefund are not supported in v2 despite appearing in the schema enum.

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 states a specific verb, resource, and channel: 'Send a document by email (Holded API v2).' It clearly separates this action from sibling document tools such as create_document, get_document_pdf, and attach_file_to_document.

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?

It provides clear usage constraints by listing supported docTypes and explicitly excluding purchase and purchaserefund in v2. It does not name alternative tools or state when to prefer this over other document actions, but the context is clear.

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