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

readOnlyHint=true already tells the agent this is a safe read, and the description adds only the endpoint path (POST /api/v2/getsalesrep), which is trivia rather than behavior. It discloses nothing about aggregation semantics, pagination beyond the schema's own max_results note, response shape, or permissions.

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 compact sentences with the purpose front-loaded and no filler. The trailing "POST /api/v2/getsalesrep" is essentially noise for an agent that only needs the tool name.

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 parameterized report with fully documented parameters and readOnly annotations, the definition covers enough to invoke it correctly. The absence of any return-shape note is a minor gap since no output schema exists, but the grouping list conveys the aggregation grain.

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 start_date, end_date, max_results and report_type are all self-documented, making 3 the baseline. The description's grouping list loosely mirrors report_type but omits type 5 ("countries (general)"), so it adds no meaning 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 ("Sales totals for a period") plus the available grouping dimensions, so an agent can tell it is a sales aggregation report. It does not explicitly contrast itself with near siblings like merit_income_statement or merit_purchase_report, so it stops short of a 5.

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 says what the report is but never when to choose it over the many other report tools (income statement, customer debts, purchase report) or what conditions/prerequisites apply. Usage is only inferable from the name and grouping list.

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