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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds real value by disclosing the returned record shape (id, type, name, addresses, phone, email, tax id, currency, payment terms, contacts) in the absence of an output schema, plus the underlying POST endpoint. It does not, however, mention the newest-first ordering or lack of page offset.

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?

Two compact sentences: resource and scope first, then returned fields, then filtering, then endpoint. Every clause carries information an agent would otherwise have to infer.

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 list tool with fully documented parameters and no output schema, the field enumeration plus filter hint cover most of what an agent needs. The remaining gap is the ordering/limit behavior, which is only documented in the schema rather than surfaced in the description.

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%, including the enum choices, filter structure and the explicit note that there is no page offset. The description's 'filter by type or words in the name' only restates what the schema already documents, 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 and resource (list clients and suppliers), clarifies that both are one record type in Megaventory, and enumerates the fields returned. An agent can distinguish it from megaventory_create_client_or_supplier and from the product-oriented list siblings.

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?

'Filter by type or words in the name' implies how to narrow results, but there is no explicit when-to-use/when-not guidance or reference to alternative tools (e.g. list_product_suppliers for supplier-product links). Usage is implied rather than stated.

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