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, but it only states that an export is created. It does not disclose whether the export is asynchronous, whether a job ID is returned, how long the export remains available, or whether this operation has side effects or replaces existing exports.

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, concise sentence with no filler. The key action and resource are front-loaded, making it immediately clear what the tool does.

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 tool with no output schema and no annotations, the description omits important workflow context. The sibling commsharbor_data_export_download strongly suggests a follow-up step, but the description never tells the agent that the export is created separately and must be downloaded later, nor what the response contains.

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%, and the only parameter, organization_id, is already described as 'Active organization ID.' The description adds no additional meaning about how the organization_id affects the export, but since the schema fully documents the parameter, the baseline of 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 uses a specific verb, 'Create', and a specific resource, 'a seven-day tenant JSON export,' which clearly distinguishes it from related tools like commsharbor_data_export_download and commsharbor_data_exports. It is not a tautology and adds detail about the export's scope and format.

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?

There is no guidance on when to use this tool versus alternatives such as commsharbor_data_export_download or commsharbor_data_exports. It does not mention that this creates a job that must later be downloaded, nor does it exclude other export paths like commsharbor_contacts_export.

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