load_file_target

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuine behavioral detail beyond that: the mapping is by name by default, and the ``mapping`` argument overrides it. It does not disclose what is returned when the table is absent or the result shape, which matters since there is no output schema.

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?

It is a single dense sentence with the core question front-loaded, and every clause carries information (existence, columns shape, mapping override). The double-backtick markup and nested parentheses make it harder to parse than necessary.

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 4-parameter read-only tool with no output schema, the description conveys intent and the override semantics but leaves return behavior implicit. An agent can infer it returns an existence answer and a mapping, yet the exact result format is undocumented, which is a residual gap.

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 0%, so the description must carry parameter meaning, and it does: it defines ``columns`` as a list of {name, index, kind, format, source} objects sourced from load_file_preview, and defines ``mapping`` as {table column: file column or null} overrides. This adds substantially more than the bare array/object schema, though ``database`` and ``table`` are only implied via the ``database.table`` notation.

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 names a specific resource (``database.table``) and two concrete operations: checking existence and computing a column mapping. It is clearly a schema-target inspection/preparation step, not a load or mutation, which separates it from siblings like load_file_start or load_file_preview. The phrasing is a question rather than a verb, which slightly weakens the statement.

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?

Usage is implied through the reference to load_file_preview as the source of ``columns``, sketching a preview-then-target workflow. However, it never states explicitly when to call this versus alternatives such as schema_explorer_table or describe_table, nor any prerequisites or exclusions.

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