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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), so the bar is lower. The description adds that identifiers are returned, and the connectionRef schema note adds useful behavioral context about session-id rotation and reusing connections, although that lives in the schema rather than the description itself.

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?

A single front-loaded sentence stating the core purpose with zero waste. It is brief to the point of being thin, but for a simple read-only list tool this is appropriately sized.

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?

Adequate for a simple read-only listing tool given strong annotations and full schema coverage, but incomplete in context: it does not explain what the returned identifiers are used for, how this relates to brc_update_allocations, or what differentiates it from brc_list_allocation_resolvers.

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% — all three parameters (bookTranId, companyName, connectionRef) are already documented in the schema. The tool description itself adds no parameter-level detail, so the baseline 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 ('Returns') and resource ('existing transaction allocations'),plus what is returned ('identifiers'). Clear enough for an agent to know the fundamental action, but does not distinguish it from siblings such as brc_list_allocation_resolvers.

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 provides no context on when to use this tool versus alternatives, no prerequisites (e.g., that a bookTranId likely comes from another call), and no mention of related allocation tools like brc_update_allocations or brc_delete_allocation_resolver.

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