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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the endpoint path and the returned field set, but says nothing about pagination semantics (next_skip), total counts, or volume limits, which are the behaviors an agent actually needs here.

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 short clauses with the resource and the payload fields front-loaded, then the endpoint. Nothing is wasted, though the field enumeration is slightly dense and the endpoint path adds little for an agent that cannot use it.

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 field list (id, number, name, legal name, RFC, email, phone, city) is the only disclosure of return shape and is genuinely useful. Annotations cover the safety profile and the schema covers all parameters, so the remaining gap is minor — pagination behavior is left entirely to the schema.

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% — top, skip, filter and orderby are each documented in detail, including OData syntax. The description adds no parameter meaning beyond that, so the baseline of 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 (suppliers/providers), enumerates the returned fields, and names the backing endpoint. The resource name is enough to distinguish it from list_clients, list_prospects and the other list_* siblings, though it never explicitly says so.

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 only implied by the verb and resource: an agent can infer 'call this to enumerate suppliers.' There is no explicit when-to-use, no exclusion of alternative tools, and no note that filtering/paging is optional.

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