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

There are no annotations, so the description carries the behavioral burden. 'List' implies a read-only enumeration, but the description does not disclose pagination, result scope beyond the tenant, whether export statuses are returned, or any side-effect guarantees. For a tool with no annotation safety net, this is too little behavioral detail.

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 single sentence contains only the essential verb and resource and is front-loaded with the action. There is no filler or redundant restatement.

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?

The tool is simple, with one required parameter fully documented by the schema, but there is no output schema and no description of what a returned export entry looks like or how this list relates to the create/download lifecycle. It is adequate for basic invocation but leaves material context gaps.

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 single parameter is described as 'Active organization ID', so the schema already documents everything needed. The description adds no parameter detail, but no compensation is required; 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 'List tenant JSON exports' uses a specific verb and resource, making the enumeration action clear. It is distinguishable from the sibling create/download export tools by verb and resource, though it does not explicitly contrast with them. Slight ambiguity remains about whether 'exports' refers to export jobs or files, so it falls short of a 5.

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?

No guidance is provided on when to call this tool instead of commsharbor_data_export_create or commsharbor_data_export_download, nor on any prerequisites such as completing an export first. The implied use case is easy to guess but not stated.

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