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

With no annotations, the description carries the full behavioral burden. It states the operation is an export producing CSV text, implying a read-only action, but does not explicitly disclose non-destructive behavior or any side effects, authentication requirements, or output limitations (e.g., max size). There is no contradiction, but the description is minimal beyond the core export function.

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, front-loaded sentence with no padding. Every clause adds specific information: the resource, the format, and the included fields. It achieves maximum economy without sacrificing clarity.

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?

Given there are no parameters, no output schema, and the tool is a straightforward export, the description covers the essential details: what is exported, the format, and the columns. It does not mention potential limitations like pagination or size, but for a log export that is a minor omission. The presence of sibling tools that summarize vs. export reduces the need for additional clarification.

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?

There are zero parameters, so the description does not need to explain inputs. The baseline for 0 parameters is 4, and the description adds value by detailing the content of the CSV export, which provides context for what the output will contain. This is sufficient.

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 states a specific verb ('Export') and a clear resource ('full lift compliance log') with an explicit output format ('as CSV text') and enumerates the content columns (operator or machine, requirement, next due, status, chase history). This is unambiguous and differentiates from sibling tools that summarize or query rather than export the entire log.

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 clearly implies this is for exporting the full log, which distinguishes it from siblings that provide summaries or filtered views, but there is no explicit statement of when to use this vs. alternatives, nor any exclusions or prerequisites. An agent would need to infer that 'full' means no filtering, but the description does not explicitly say 'use this instead of search_requirements for a complete export'.

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