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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state whether the tool is read-only, whether it has side effects, what permissions are needed, or what happens on invocation. The mention of 'payment history as read-only records' describes imported data, not the tool's own behavior.

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 a single sentence and front-loads the primary subject ('Fields for importing history from another system'). The parenthetical enumeration is dense but earns its place by listing the covered data domains and presets.

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?

An output schema exists, so return-value structure need not be explained. However, with zero annotations and no explicit verb or usage guidance, the definition leaves the agent to infer the operation and its read-only nature, which is a meaningful gap for a tool definition.

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 has zero parameters, so parameter semantics are not applicable; the baseline is 4. The description adds no parameter detail, but none is needed.

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 the domain clearly: fields for importing history from another system, including jobs, quotes, invoices, price book, equipment, maintenance plans, and payment history, plus jobber and housecall_pro presets. However, it is a noun phrase with no operation verb, so an agent must infer whether the tool lists, returns, or defines these fields. It does distinguish the history-import scope from siblings like imports_fields and imports_historyRun, but the action is not explicit.

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 explicit guidance on when to use this tool versus imports_fields, imports_historyPreview, imports_historyRun, imports_paymentHistory, or imports_preview. The phrase 'importing history' implies a pre-import metadata lookup, but no conditions, exclusions, or alternatives are stated.

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