Get customer profile

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

Annotations already declare readOnlyHint=true and openWorldHint=false. The description adds a specific behavioral limit: 'the 20 most recent bookings', which is not captured in annotations. It also clarifies the output scope by listing fields. This adds value beyond annotations, though it does not discuss error handling or authentication.

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, front-loaded sentence that states the purpose and then lists the returned data. Every word is informative with no redundancy or filler.

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 simple read operation with one parameter and no output schema, the description covers the main aspects: what is returned and the booking limit. It does not describe the response structure, but the enumerated contents are sufficient for an agent to understand the output. The lack of pagination details is acceptable given the '20 most recent' limit.

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 schema defines customer_id as a required integer with constraints. The description does not discuss the parameter, but the parameter is self-explanatory from its name and the schema fully documents it. With only one parameter and complete schema coverage, the description does not need to elaborate, so a baseline of 3 is appropriate.

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 verb 'get' and the resource 'customer profile', and enumerates the contents (contact details, notes, visit and spend totals, no-shows, and 20 most recent bookings). This distinguishes it from search_customers (which implies searching multiple) and create_customer (creation).

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 does not explicitly mention when to use this tool versus alternatives like search_customers. It simply states what it returns, leaving the usage context implied. There is no mention of prerequisites (e.g., needing a customer ID from a search) or when not to use it.

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