brc_list_purchases

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It merely states that it 'lists purchases' but does not explain pagination behavior, read-only nature, or any side effects, leaving critical safety traits undisclosed.

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 extremely concise (5 words), but this brevity results from under-specification rather than efficient communication. It lacks necessary details, making it insufficient for an agent to understand the tool's full behavior.

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?

Given the tool's complexity (7 parameters, no output schema, no annotations), the description is severely incomplete. It omits information about return values, pagination defaults (pageSize of 20), required companyName context, and how filtering/ordering work, leaving substantial gaps.

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?

The input schema has 7 parameters but only 43% have descriptions (filter, orderBy, companyName). The description adds no additional meaning beyond what is already in the schema, failing to compensate for the low coverage by explaining the role of top, page, skip, and pageSize.

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 'Lists BRC purchases' clearly states the verb and resource, making the basic purpose understandable. However, it does not specify any scope or distinguish it from sibling list tools, reducing its helpfulness for tool selection.

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?

No guidance is provided on when to use this tool versus alternatives like brc_list_payments or other list tools. The description lacks any contextual clues about prerequisites or filtering capabilities, leaving the agent without usage direction.

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