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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description does add real value with the permission prerequisite "Requires items.read," which the annotations do not convey. However it says nothing about pagination, result limits, or how archived and active suppliers are ordered or interleaved.

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 short sentences with no filler and the permission requirement front-loaded, which is good ordering. But the terseness here is under-specification rather than economy — the sentences are short because essential information is absent, not because the tool is simple.

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 and 0% schema description coverage, the description carries the burden of explaining both parameters and the return shape. It explains neither include_archived nor whether results are paginated, truncated, or ordered, which for a list endpoint is a material omission.

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 0% for both parameters, so the description must compensate and only partly does: "Search only matches name" usefully bounds what the search string matches against. The include_archived parameter is never explained, leaving its default (are archived suppliers returned or excluded?) entirely unknown despite being the only behaviorally significant flag.

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?

"List suppliers" restates the tool name and title verbatim, adding no scope, filtering, or ordering information. The only content beyond the name is "Search only matches name," which is a parameter detail rather than a purpose statement, so an agent learns nothing new about what this returns compared to list_customers or list_items.

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?

There is no when-to-use guidance and no mention of alternatives such as search_items or the sibling list_* tools, nor any exclusion of when this is the wrong choice. The single hint that search matches only the name is a usage-adjacent detail but does not tell the agent when to reach for this tool versus another.

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