get_headers

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

Describes return values and warns about other tools' error behavior. No annotations provided, but description covers key behavioral aspects. Could mention read-only nature explicitly.

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 fluff. Front-loaded with functionality and usage advice.

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 tool simplicity (one param, likely simple output), description covers purpose, usage context, and return values adequately. Output schema existence reduces burden.

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?

Only parameter 'file_path' not described beyond name; schema coverage is 0%. Though context implies it's a file path to an export, explicit description would improve clarity.

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?

Explicitly states it returns column headers with spreadsheet letters and header_row. Clearly distinguishes from siblings by advising to call it before query_export or aggregate_export when column names are unknown.

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?

Provides explicit guidance: use when you don't know column names, as other tools error on typos. Describes the purpose in context of sibling tools.

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