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

The annotations already provide readOnlyHint=true and destructiveHint=false, so the description adds no behavioral transparency beyond those structured values. It does not mention pagination behavior, filtering, the required company context, or how the connectionRef should be reused.

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 or repetition. It is concise, though it trades informational richness for brevity.

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 tool with 8 parameters and no output schema, this description is under-specified. It does not explain what the returned list contains, how pagination and filters work, or that a companyName and stable connectionRef are prerequisites.

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 only 50%, and the description contributes no additional parameter explanation whatsoever. The agent must rely on parameter names and types for top, page, skip, and pageSize, because those have no descriptive help in the schema or description.

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 clear verb-plus-resource structure: 'Lists BRC sales reps.' An agent can immediately identify this as a collection/read operation for sales representatives, and it is distinct from get/create/update/delete sales-rep siblings. It stops short of a 5 because it provides no scope or filter context that would distinguish it from similar list_* tools.

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 description gives no explicit guidance about when to use this tool instead of brc_get_sales_rep, brc_batch_sales_reps, or other listing tools. Any usage context is only implied by the tool name and title.

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