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

Annotations declare readOnlyHint=true, so the safety profile is covered; the description goes beyond that by enumerating the returned payload (payment method, amounts, refund status, every designation type), which is the only disclosure of return content since no output schema exists. It omits error/not-found behavior and permission requirements, so it stops short of a 5.

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 tightly packed sentences, with the resource and returned fields front-loaded and the API endpoint appended as reference. Nothing is wasted.

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?

With no output schema, the description sensibly compensates by naming the returned fields, and the endpoint path aids orientation. It is nearly complete for a single-read tool, lacking only failure-mode behavior (invalid or missing id) and auth expectations.

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 coverage is 100% and the schema already documents that the id is the API Id rather than the CRM AccountNumber, so the description adds no parameter meaning beyond it. Baseline 3 is appropriate when the schema does all the work.

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?

Specific verb ('Fetch one transaction') plus the exact resource and the fields it returns (payment method, amounts, refund status, designations). The singular scope cleanly distinguishes it from bloomerang_list_transactions without opening either schema.

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 when-to-use guidance and no routing to alternatives — it never says to call bloomerang_list_transactions first to obtain a transaction_id, nor what to do when the id is unknown. The single-use case is implied by the name, but nothing is stated.

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