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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered and the description need only add operational context. It instead adds a generic approval-policy sentence that has no bearing on a read operation and says nothing about pagination caps, default page size, or search matching 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?

Three short sentences, but the third (approval configurability) is boilerplate that earns no place in a read-only listing tool, and the first is oddly worded around 'purchase_lists records' instead of front-loading what the tool returns.

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 values need not be described, but for a 4-parameter, 0%-coverage tool with a required identifier the description leaves the agent without enough to call it confidently — it never ties the call to a purchase template nor explains pagination.

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 description coverage is 0% across 4 parameters, and the description mentions none of them — notably the required templateId UUID, which is the one parameter an agent could get wrong. limit/offset/search are partly self-explaining via defaults and bounds in the schema, but the description contributes zero semantic meaning of its own.

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 verb+object ('Read template line items') is legible, but 'template' is never qualified as a purchase template, and the opening sentence references 'purchase_lists records' rather than naming the resource unambiguously. With siblings like list_purchase_templates, list_purchase_items and get_purchase_template present, the description does nothing to distinguish this tool from them.

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?

'Use this when working with RetailHardHat purchase_lists records in the connected organization' gives a loose contextual trigger but names no alternative tool and no exclusion condition (e.g. when to use list_purchase_items or get_purchase_template instead). Usage is only implied.

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