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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only nature is fully covered. The description does not add behavioral detail like not-found behavior or company context requirements, but it also does not contradict the annotations.

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 a single sentence with no wasted words. 'Gets one BRC supplier by id' is direct, front-loaded, and perfectly sized for a simple getter.

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 basic get-by-id operation, the description plus the rich schema and read-only annotations is largely complete. The only missing context is explicit handling of missing/empty results or the reason for the required companyName, but these are minor given the full schema descriptions.

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 each parameter is already documented in detail. The description adds no parameter-specific guidance beyond 'by id', but the schema already carries the full semantic burden for id, companyName, and connectionRef.

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 uses a specific verb ('Gets'), a specific resource ('one BRC supplier'), and the lookup criterion ('by id'). It clearly distinguishes this tool from listing tools like brc_list_suppliers and brc_batch_suppliers, so an agent can immediately understand it is the single-item lookup.

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 context is implied: use this when you need one supplier by id. However, the description does not explicitly mention alternatives or say when not to use it, such as when retrieving opening balances or supplier lists. The agent must infer the appropriate context.

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