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

Annotations already declare readOnlyHint=true, idempotentHint=true and non-destructive, so the safety profile is covered. The description adds only the 'newest first' ordering context; it says nothing about pagination defaults, page size behavior, or whether results are tenant-scoped.

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 short sentence with zero waste, front-loading the verb and the ordering. It is efficient but so terse that it omits context an agent would want before calling.

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 should at least characterize the shape or scope of returned rows, which it doesn't (the schema does explain the envelope variation). Annotations cover safety and the schema covers parameters, so it is minimally adequate but leaves real gaps about what these settings are.

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% and both parameters (limit, cursor) are fully documented in the schema, including the bare-array vs. cursor-envelope distinction. The description adds no parameter meaning beyond that, so the 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?

States a specific verb ('List') and resource ('sales_settings rows') plus a sort order ('newest first'), so the agent knows it's a collection read. It does not, however, clarify what a sales_settings row represents or how it differs from siblings like sales_settings_read or sales_settings_numbering_read.

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?

No when-to-use guidance and no mention of alternatives such as sales_settings_read (single row) or sales_settings_upsert (write). The only implicit signal is 'newest first', which merely hints this is a bulk listing rather than a targeted fetch.

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