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

The readOnlyHint and destructiveHint annotations already establish the safety profile, but the description adds no behavioral context beyond them. It does not disclose pagination behavior, output format, or anything about the required company connection.

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?

The description is short, but it is under-specified rather than genuinely concise. For a tool with 8 parameters and an important connectionRef requirement, a single generic sentence is not sufficiently informative.

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 no usage guidance, the description is incomplete. It leaves an agent to infer pagination behavior, output shape, how to choose among related supplier tools, and whether a connection must be established beforehand.

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?

The description adds nothing about parameters, and the schema only describes 50% of them. Pagination parameters such as top, page, skip, and pageSize have no semantic explanation, and the description does not compensate for that gap.

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?

The description states a concrete verb and resource: it lists BRC suppliers. This distinguishes it from create, update, delete, get, and batch supplier tools, though it does not explicitly distinguish it from other list-type supplier 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?

No guidance is provided about when to choose this tool over brc_batch_suppliers, brc_get_supplier, or the many other list tools. The description does not mention filters, pagination, or the company-connection prerequisite.

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