List DATEV EXTF columns

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

Annotations already declare readOnlyHint=true, and the description's 'List' verb aligns with this. The description adds useful context about the file formats, column counts, and the fact that columns come from line 2, which goes beyond the structured annotations.

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 zero redundancy. The first sentence front-loads the action and resource; the second provides concrete use cases. Every word earns its place.

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 simple one-parameter tool with an output schema, the description covers what the tool does, what parameter values mean, and when to use it. Minor gap: it does not specify indexing (0- or 1-based) for 'numbered by position,' but the output schema likely covers the return structure.

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%, but the description fully compensates by explaining both enum values: Buchungsstapel (Formatversion 13, 125 columns) and Debitoren/Kreditoren file (254 columns). This gives the agent semantic understanding of what each 'format' value means beyond the bare enum labels.

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 opens with a specific verb 'List' and specifies the resource: columns (line 2) of DATEV Buchungsstapel or Debitoren/Kreditoren files. It distinguishes itself from siblings by the action (list vs validate/explain/write) and includes concrete details like column counts and format version.

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 explicitly states when to use the tool: 'to map export fields to DATEV columns or to find a column named in a finding.' It does not mention alternatives or when not to use it, but the sibling tools are action-distinct, so the implied usage is clear.

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