get_cleaning_report

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

No annotations are provided, so the description carries the burden. It tells us the report is a result of the most recent clean_csv call, but doesn't disclose what the report contains, how long it's retained, or if it errors if no clean_csv has been called.

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?

A single, clear sentence. No wasted words. Perfectly concise.

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 zero-parameter getter tool, the description does its job, but could mention what the report contains or what happens if no clean_csv call has been made. Since there's no output schema, a bit more detail on the report structure would have been helpful.

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?

With 0 parameters, there is no parameter semantics burden on the description. The description correctly focuses on the return value since there's nothing else to explain.

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 that the tool returns a before/after report from the most recent clean_csv call, which is specific about what it returns. However, it could be clearer on what 'before/after' encompasses and how it differs from siblings like inspect_csv.

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 implies this tool is for after a clean_csv call, but it doesn't explicitly state when to use it versus alternatives. However, the phrase 'most recent clean_csv call' provides useful context.

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