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

With no annotations provided, the description carries the full burden. It adds meaningful behavioral context: files expire after 7 days and that durable audit and row-level results persist beyond the file. This goes beyond a simple 'download' and helps set expectations about the data's lifecycle, though it does not explicitly state the operation is read-only.

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?

Two concise sentences with the primary action front-loaded. Every phrase adds value: the action, the expiry warning, and the persistence note. No fluff or repetition.

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 download tool with only two parameters and no output schema, the description covers the essential context: the file type, expiration, and what data persists. It does not describe the response format, but that is likely self-evident for a file download. Minor omission given the low complexity.

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% and both parameters (file_id, organization_id) are already described. The description adds no additional semantic detail about the parameters, so it meets the baseline but does not enhance understanding beyond the schema.

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 clearly states the action 'Download a tenant CSV' with a specific resource, but does not explicitly differentiate from sibling download tools like commsharbor_data_export_download or commsharbor_contacts_export. The 'tenant' qualifier is slightly ambiguous but the intent is clear enough.

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 contextual guidance ('before expiry') and explains the 7-day expiration, but it does not mention when to avoid this tool or name alternative tools. There is no explicit routing, so an agent might not know this is the right download for contact files specifically.

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