suppliers_list

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds genuinely new context: suppliers are auto-provisioned from incoming invoices via ANAF e-Factura sync, which explains why records the agent didn't create exist and why counts may change between calls.

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, front-loaded with the core action, then context, then capabilities. No filler, though the provenance sentence sits slightly ahead of the more operationally useful search note.

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 read-only paginated list tool with a fully documented schema and safety annotations, the description covers purpose, provenance and search. Missing only minor operational details such as default page size and return shape, which the schema largely covers.

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 all four parameters (page, limit, search, companyId) are already documented. The description restates the search fields (name, CUI, email) but adds nothing about pagination or the companyId override, so 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 and resource ("List suppliers") plus a scope ("for the selected company") and an ordering behavior ("grouped alphabetically"). It is distinguishable from clients_list by resource, but does not explicitly disambiguate against siblings like suppliers_export_csv or suppliers_get.

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?

Usage is implied: fetch the supplier catalog, with search supported. There is no explicit when-to-use/when-not guidance, no pointer to suppliers_get for details or suppliers_create for manual creation, even though several sibling tools operate on the same resource.

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