Import Parquet to Table

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

No annotations provided, so description carries full burden. It discloses that it reads from S3, imports into existing table, and requires schema compatibility. However, it omits details on failure behavior, idempotency, permissions, or whether data is appended or replaced. Adequate but lacks depth.

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, front-loaded with the action. No redundant words. Every sentence adds value: first the action, then prerequisites.

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?

No output schema, so description should clarify return value (e.g., success, row count). It doesn't. With 10 parameters, description is brief and doesn't explain parameter interplay. Sibling tools are not contrasted. However, core flow is sufficiently covered.

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?

Input schema has 100% description coverage, providing baseline of 3. Description adds no parameter-specific semantics 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?

Description clearly states it imports Parquet data into an existing S3 table, with specific verb 'imports' and resource 'S3 table'. It distinguishes from siblings like import_csv_to_table (CSV) and create_table (table creation) by specifying Parquet and existing table requirement.

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 usage context: table must exist and schema compatibility required. It implicitly differentiates from CSV import, but does not explicitly mention when to use alternatives. No exclusions or alternative tool names are given.

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