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

No annotations are provided, so the description carries the full burden. It does add one behavioral detail: exports are 'retained for seven days', which is useful. However, it does not explicitly state that the operation is read-only (though 'List' implies it), nor does it address authentication, rate limits, or response shape. This is moderate transparency for a simple list tool.

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 sentence that front-loads the core action ('List the tenant data exports') and appends a concise retention note. There is no filler, redundancy, or irrelevant detail; every word serves a purpose.

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 list operation with one well-documented parameter and no output schema, the description provides the essential action and a relevant retention detail. It does not describe the response format, but an agent can reasonably infer a list of export records. The only notable gap is the lack of usage context relative to sibling export tools, which is covered under usage_guidelines.

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 only parameter, organization_id, has 100% schema description coverage ('Active organization ID'). The description itself adds no additional parameter semantics, so the baseline of 3 applies. The agent can correctly populate the parameter from the schema alone.

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 starts with 'List the tenant data exports', clearly stating the action (list) and resource (tenant data exports). It is implicitly distinguished from sibling tools like commsharbor_data_export_create and commsharbor_data_export_download by the verb and scope, and the retention detail adds useful context without ambiguity.

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 gives no explicit guidance on when to use this tool versus alternatives like data_export_create or data_export_download. It does not mention any exclusions, prerequisites, or suggest that this tool should be used to locate exports prior to downloading. The only implied usage is the literal 'list' action, which is not sufficient guidance for tool selection.

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