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

Annotations already declare readOnlyHint=true, so safety is covered. The description's additional facts (30 per page, active-by-default, XML endpoint) largely restate what the input schema already documents for `page` and `which`, so marginal behavioral value is low.

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?

Three compact sentences, front-loaded with the resource and its domain meaning, then defaults. The trailing 'Kickserv: GET /{account}/items.xml' adds little for an agent choosing a tool, but it costs almost nothing.

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?

Zero required parameters, a simple read-only list, and pagination/default-filter behavior all stated — enough to call it correctly. With no output schema, the description could say more about what each listed item contains, but the omission is minor for a catalog list.

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%: name, page, and which are all documented in the schema, including the 30-per-page behavior and the active/inactive/all enum. The description repeats rather than extends 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 clear verb (List) and resource (products/services), and adds the disambiguating gloss 'the price list used for job charges' so the agent knows 'items' means billable catalog entries. No sibling tool overlaps this resource, so explicit sibling differentiation isn't needed, but none is offered either.

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?

'Active items only by default' implies the common case and hints that the `which` parameter changes it, which is implied usage guidance. It never states when to reach for this tool versus e.g. kickserv_list_customers or job lists, nor any prerequisites.

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