import_toast_csv

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

No annotations present. Description discloses auto-scanning behavior but omits details on file format expectations, success/failure outcomes, overwrite behavior, permissions required, or idempotency. For a mutation tool, this is insufficient.

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 sentences with no wasted words. First sentence states core purpose, second adds key details (auto-scan, accepted types). Front-loaded and efficient.

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 two optional parameters and no output schema, the description covers core functionality: import CSV, auto-scan folder, acceptable report types. It omits file format constraints and outcome details but is still largely complete for a simple import tool.

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%, with both parameters described in the schema. The description repeats the file_path schema text, adding no new meaning. It does not mention business_name parameter, so no extra value beyond 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?

Description clearly states the tool imports a Toast POS CSV export, specifies verb 'import' and resource 'CSV export.' It lists accepted report types (labor, sales summary, server sales), distinguishing it from sibling read tools like get_sales_summary.

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?

Description provides context on when to omit file_path (auto-scan folder) and lists accepted CSV types. It implicitly differentiates from siblings as an import tool, but lacks explicit when-not-to-use or alternative suggestions.

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