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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description aligns with these. However, the description adds no additional behavioral context such as error behavior, missing-id semantics, or how the returned sales rep is structured.

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, front-loaded sentence with no filler. It directly states the action, target, and filter, and every word contributes to understanding the tool.

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 simple read-only point lookup, the description plus the fully documented input schema is sufficient for an agent to call the tool correctly. The main gap is not describing the response shape or not-found behavior, but this is minor for a get-by-id tool with no output 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%, so all parameters (id, companyName, connectionRef) already have their semantics defined. The tool description adds no extra parameter-level context beyond what the schema provides, so it stays at the baseline.

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'), names the resource ('one BRC sales rep'), and explicitly identifies the lookup key ('by id'). This makes it clearly distinct from sibling tools like brc_list_sales_reps, brc_create_sales_rep, brc_update_sales_rep, and brc_delete_sales_rep.

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?

The phrase 'by id' implies this tool is for retrieving a single sales rep, but it does not explicitly state when to use it over brc_list_sales_reps or mention any exclusions. Usage context is implied rather than clearly defined.

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