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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuine context beyond that: the 31-day hard window, the effective 100-row cap when line items are requested, and the warning that responses contain shoppers' personal data. It does not describe pagination behavior beyond the schema, keeping it out of 5 territory.

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?

It is a compact, front-loaded block that leads with the verb and resource, then scope, then return content, then caveats. The inline division-code gloss partly duplicates the enum documentation, which is minor waste but not damaging.

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 an 11-parameter read tool with no output schema, the description usefully summarizes the returned fields, the window constraint, the line-item tradeoff and the privacy caveat. Only the routing to the single-receipt sibling is left unstated.

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 100%, so the schema already explains every parameter including defaults, pagination and the division enum. The description largely restates the division codes and the with_details limit cap that the schema already spells out, adding little new semantics; baseline 3 applies.

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 uses a specific verb and resource ('List sales transactions (receipts)') and scopes it to a window of at most 31 days, then enumerates the returned fields. It separates itself from the singular smaregi_get_transaction only implicitly by being a windowed list, and never names the sibling directly, so it falls 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 31-day window bound and the note that requesting line items caps the limit at 100 do give some operational guidance, and the personal-data warning signals caution. However, there is no explicit statement of when to prefer this over smaregi_get_transaction or how the optional filters (customer_code, store_id, transaction_uuid) change the mode of use.

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