pull_transactions

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

No annotations are provided, so the description must fully disclose behavior. It states the tool fetches transactions, but does not mention whether it is read-only, how pagination behaves, whether shortCode is required/optional, or what the response looks like. This leaves significant behavioral assumptions unaddressed.

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 two sentences: the first states the action and scope, the second provides a practical use case. Every word adds value, and the structure is front-loaded with the core 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 4-parameter tool with no output schema and no annotations, the description gives a clear purpose and usage context. However, it omits behavior around pagination, shortCode semantics, and return format, which are needed for fully confident invocation. It is adequate but not comprehensive.

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 schema already documents startDate, endDate, and offsetValue well. The description reinforces the time-window semantics. However, shortCode has no schema description and the description does not clarify its purpose, leaving an ambiguity that the schema and description together fail to resolve.

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 uses a specific verb ('Fetch') and resource ('C2B transactions') with a clear scope ('for a time window'). It distinguishes pull_transactions from siblings like list_callbacks and transaction_status by focusing on C2B transaction retrieval.

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?

It explicitly states a use case: 'Useful for reconciliation when callbacks were missed.' This gives clear context for when to use the tool. It does not mention exclusions or alternatives, but the primary usage scenario is well covered.

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