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

Annotations cover the safety profile (readOnly, non-destructive, openWorld), and the description adds context they don't carry: an authorization requirement, a required Cotlet API key scoped to the app, and the lockboxes date-range caveat. It stops short of describing export processing (async vs sync) or whether the download link expires. The phrase 'Creates a Data Export' sits in mild tension with readOnlyHint=true, but materializing a report artifact is conventionally still a read, so it is not a contradiction.

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?

Purpose is front-loaded and the sentences are short, but the text repeats itself: the CSV download link twice, the admin restriction twice, and the categories twice. Trimming the duplication would lose no information.

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?

With no output schema, the description correctly states the return shape (CSV download link) and covers auth, valid categories and the lockboxes date caveat, which is enough to invoke it. It leaves out failure behavior for non-admins and how quickly the export is ready.

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%, so the schema already documents all three parameters, including the enum values and the 'Not used for lockboxes' notes. The description merely restates those same facts, adding no syntax or format detail beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ('Creates a Data Export for one category and returns a CSV download link') and names the three exportable categories. No sibling tool in the Rently family exports report data, so the agent can route on it immediately.

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?

Gives real preconditions: one category per call, the valid category values, admin/super-admin only, and the exception that the date range doesn't apply to lockboxes. It does not, however, say when not to use it or point to an alternative for other data needs.

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