unused_columns

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

With no annotations provided, the description discloses case-insensitivity and staleness detection behavior. However, it does not mention permissions, error handling, or side effects. The description adds some behavioral context beyond the schema but is not fully comprehensive.

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?

The description is concise, uses a clear docstring structure with bulleted Args, and front-loads the core purpose. One sentence could be slightly more direct, but overall 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?

The description covers parameter semantics and some behavioral context, but lacks information about the output format (e.g., list of column names), pagination, or error cases. Given no output schema, this is a notable gap for a query 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 coverage is 0%, so the description carries the full burden. It explains each parameter's purpose, case-insensitivity, format (e.g., 'Sales.qvd'), and the optional lineage_activation_date's effect on staleness detection, adding significant meaning beyond the schema types.

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 the tool returns columns of a data file that no app consumes, using specific verb-resource combination. This is distinct from the sibling tool 'ghost_files', which likely deals with unused files, not columns.

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 usage for finding unused columns and explains parameter constraints, but does not explicitly state when to use this tool versus the alternative 'ghost_files' or provide when-not-to-use guidance.

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