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

With no annotations provided, the description carries the full burden of behavioral disclosure. It conveys that the result is a JSON export, that it is scoped to a single tenant, and that it has an expiration window – all useful behavioral traits beyond the schema. However, it does not disclose what happens when the export has expired or what the exact response format is.

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, front-loaded sentence with no filler. Every word adds meaning, and the core action and object appear first.

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 simple two-parameter download tool, the description covers the essentials: what is downloaded, its scope, and its expiration risk. However, it omits how to obtain a valid export_id and does not describe expiration error behavior, which would matter to an agent trying to invoke the tool correctly. With no output schema, a bit more context about the expected result would be helpful.

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 schema already documents both parameters at 100% coverage ('Tenant export ID' and 'Active organization ID'), so the description has little to add. The description gives no additional detail about where export_id comes from or how organization_id is resolved, but the baseline of 3 is appropriate given the schema's full coverage.

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 uses a specific verb ('Download'), a clear resource ('one tenant-scoped JSON export'), and a distinctive constraint ('before it expires'). This makes the tool's purpose unmistakable and naturally distinguishes it from create/list siblings like commsharbor_data_export_create and commsharbor_data_exports.

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 phrase 'before it expires' implies a timing-related usage condition, but the description does not explicitly say when to use this tool versus alternatives, nor does it mention that the export_id likely comes from a preceding create/list step. An agent can infer the usage context, but the guidance is not explicit.

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