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

With no annotations, the description carries the behavioral burden. 'Public' indicates accessibility and 'totals only' discloses that itemized transaction details are not returned, which are useful constraints. However, it omits details like response format, data freshness, or any rate limiting.

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 extremely compact and front-loaded. Every word contributes meaning: 'public' gives access scope, 'sales ledger' identifies the resource, and 'totals only' sets output expectations.

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 zero-parameter, simple read-oriented tool, the description covers the essential points: what resource is involved and what kind of data to expect. It does not specify formatting or exact return fields, but 'totals only' gives enough orientation for an agent to invoke it appropriately.

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 tool has zero parameters, so the baseline is 4 per the rubric. There is no parameter documentation burden, and the description does not need to compensate for schema gaps.

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 identifies the resource as the public sales ledger and adds the scope 'totals only,' which distinguishes it from catalog-like siblings. It lacks an explicit verb such as 'retrieve' or 'return,' so it stops short of a perfect 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 phrase 'sales ledger — totals only' implies this tool is for aggregated sales data, but there is no explicit statement of when to use it over alternatives. None of the sibling tools are mentioned, and no when-not-to-use guidance is provided.

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