customer_overview

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

With no annotations, the description carries the full burden. It discloses the required input type and lists the returned data categories. It does not explicitly state whether the tool is read-only or what happens if the ID does not exist, but the described behavior ('full card') implies a read operation. Slightly more detail on error handling would push it higher.

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, perfectly front-loaded: the first sentence states the tool's purpose and contents; the second gives prerequisite and alternative. Every word earns its place with no redundancy.

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 single-parameter tool with an output schema, the description covers all necessary context: what data is returned, what input is needed, and when to use a different tool. The presence of an output schema means return values need not be spelled out. This description is complete and self-sufficient.

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% (no parameter description), so the description must compensate. It adds key meaning by specifying the customer_id must be a 'ServiceTitan customer id', which distinguishes it from other possible identifiers. It stops short of providing examples or format hints, but the single parameter is adequately clarified.

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 a specific function: returns a 'full card' for one customer, enumerating contents (contacts, locations, 5 recent jobs, external ids). This is distinct from sibling tools like find_customer (search by name/phone) and job_detail (single job focus).

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 when-to-use guidance: 'Needs a ServiceTitan customer id' and gives a direct alternative: 'use find_customer if you only have a name or phone.' This tells the agent exactly when to choose this tool over a sibling.

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