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

readOnlyHint=true already covers the safety profile, and the description goes beyond it by disclosing the default response composition (SaleLines+Item, SalePayments+PaymentType, Customer) and the underlying endpoint — meaningful since there is no output schema. It does not mention the rate-limit cost of relations or not-found behavior, which the schema carries alone.

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?

A single front-loaded sentence naming the resource, the key, and the payload, capped by the endpoint string. The endpoint is mildly redundant but serves as traceability rather than 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?

With no output schema, the description correctly compensates by describing what comes back by default, which is the main thing an agent needs. Only edge behavior (missing sale, rate-limit consequences of expanding relations) is left unstated, a minor gap for a read-only fetch.

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 100%, so both parameters are fully documented in structured data and the baseline applies. The description only echoes saleID and restates the default relations, adding no syntax or trade-off information beyond the schema.

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?

States a specific verb and resource ('One sale by saleID') plus the exact payload assembled (line items, payments, customer), which separates it cleanly from lightspeedrseries_list_sales and the other get_* siblings. The raw endpoint path reinforces the resource identity.

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?

Usage is implied rather than stated: an agent can infer this is the single-record fetch to use after listing sales, but the description never says so or names an alternative. The pointer to list_sales lives only in the schema's sale_id description.

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