brc_get_prepayment

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

With no annotations, the description adequately indicates a read operation and a behavioral constraint about child prepayments. It does not mention permissions or error conditions, but for a simple get tool this is sufficient.

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?

Two sentences with no unnecessary words. Efficiently conveys the core purpose and key limitation.

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?

Description is adequate for a straightforward get tool with well-described parameters. However, the absence of an output schema and lack of detail on returned fields may leave some ambiguity, but overall it is sufficiently complete.

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?

Input schema has 100% description coverage for both parameters (id and companyName). The description adds no additional parameter details beyond the schema, so baseline score of 3 is appropriate.

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 clearly states the tool returns information about a single parent Prepayment by id, and explicitly notes that child prepayments are not exposed. This clearly distinguishes it from list tools and other prepayment 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 implies when to use (get a specific parent prepayment) and notes a limitation (no child prepayments), but does not explicitly state alternatives like the list tool brc_list_prepayments for browsing multiple prepayments.

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