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

No annotations exist, so the description carries the full behavioral burden, and it discloses almost nothing. It is implicitly a read operation returning preset-to-export-column mappings, but it never states that it is read-only, whether the presets are static or shop-specific, or how large the response is.

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 short and front-loads the resource, which is good, but it is a sentence fragment with an awkward trailing clause ('the export column each reads') that forces the reader to re-parse what the mapping direction actually is.

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?

This is a simple zero-parameter lookup with no output schema, so the description is the only source of information about the response — and it does not say what shape the result takes (a field list, a preset-to-column map, or both). Missing that plus any usage context leaves an agent guessing.

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?

The tool takes zero parameters, so there is no parameter meaning to add; baseline 4 applies. The description correctly implies no input is needed by framing the result as a fixed catalogue of presets.

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 — customer import fields plus the built-in presets (jobber, housecall_pro, servicetitan, companycam) and their export columns — which does distinguish it from siblings like imports_historyFields and imports_paymentHistory. However it is a noun phrase with no verb, so an agent cannot tell whether this lists, gets, or generates the mapping.

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?

There is no when-to-use guidance at all: no statement of the task this supports (e.g. discover which customer columns an import expects before calling imports_preview or imports_run), no prerequisites, and no named alternative among the imports_* siblings.

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