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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds no additional behavioral context such as output format, ordering, filtering, or side effects; it merely restates the operation. The 'eligible for allocation updates' clause describes selection criteria, not behavior beyond 'returns.'

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. Every word contributes meaning, and it is as concise as possible while still conveying the tool's purpose.

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 list tool with fully documented parameters and read-only annotations, the description is mostly adequate. However, there is no output schema and the description does not clarify what a 'receiver transaction' is or how the returned data feeds into allocation updates, which would help an agent use the tool correctly in a workflow. A bit more context would improve completeness.

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 the schema fully documents all parameters (bookTranId, companyName, and connectionRef). The description does not add any parameter-level guidance beyond what the schema already provides, so it meets the baseline for a fully-documented schema.

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 specific verb ('Returns') and a specific resource ('receiver transactions eligible for allocation updates'), so an agent can tell what the tool does without opening the schema. It does not explicitly differentiate itself from similar list tools like brc_list_allocated_transactions or brc_delete_allocation_resolver, so it is clear but not fully sibling-distinct.

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 'eligible for allocation updates' strongly implies this tool is a precursor to brc_update_allocations, but it does not explicitly state when to use this tool versus alternatives or when not to use it. No exclusions or alternative tools are named, so usage context is only implied.

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