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

readOnlyHint=true already declares this as a safe read. The description adds value by disclosing the shape of the returned record (designations, acknowledgement status, refund status), which is useful since there is no output schema, but it says nothing further about auth, errors, or missing-record behavior.

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 tight sentences that front-load the operation and payload before the endpoint mapping. Nothing is padded, though the trailing endpoint string is mildly redundant for an agent.

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 single-parameter read with no output schema, the description usefully enumerates what the returned transaction contains, which partly compensates for the absent output schema. It is nearly complete, missing only an explicit routing note against the list sibling.

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 itself documents the key nuance (API Id, not CRM AccountNumber). The description adds no parameter detail beyond what the schema already provides, 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 (Fetch) and resource (one transaction) and enumerates the notable payload sub-resources (payment method, amounts, refund status, designations). It is clearly distinguished from bloomerang_list_transactions by the singular 'one transaction', though it does not name that sibling explicitly.

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?

Usage is only implied: 'one transaction' combined with the required transaction_id signals this is the single-record lookup, versus the list tool. There is no explicit statement of when to prefer this over bloomerang_list_transactions or any precondition guidance.

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