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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the GET endpoint, which confirms a pure read, but says nothing about aggregation semantics (what a 'total' includes, whether date_from defaults, pagination, or result shape). Some added value, but well short of full behavioral disclosure.

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 dense sentence that front-loads the operation and result type, then the grouping options, then the filters, then the endpoint. The twelve-value enumeration is verbose but directly encodes what the agent must pass, so it earns its place; only minor trimming is possible.

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 7 parameters at 14% description coverage and no output schema, the description leaves important gaps: the return shape of the aggregated report is undisclosed, the filter parameters are only gestured at, and there is no indication of date-range behavior. It is not sufficient to call this tool confidently without inspecting the schema.

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 only 14% of 7 parameters, so the description must carry the load and largely does not. It enumerates the group_by values (already present in the enum) and mentions 'date range and optional filters' generically, without explaining how date_from/date_to are bounded or that product_id/customer_id/salesman_id/branch_id act as restrictive filters and how they combine.

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 ('Invoiced sales totals') plus the full enumeration of valid groupings and the backing endpoint GET /reports/sales/invoices/{group}. This clearly separates it from the sibling list tools (e.g. laudus_list_sales_invoices) which return individual records rather than aggregates.

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 implies the usage context (aggregated reporting over a date range with optional filters), but never states when to choose this over siblings like laudus_profit_and_loss or laudus_list_sales_invoices, nor any prerequisites or exclusions. Usage is inferable but not guided.

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