getOperations

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Get recent operations,' which implies a read operation but doesn't mention ordering (e.g., newest first), pagination, potential empty results, or any side effects. The description adds little beyond what the tool name already implies.

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?

A single, concise sentence that immediately states the action and target. There is zero wasted text, and the essential information is front-loaded.

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 low-complexity tool with only two parameters, no output schema, and no nested objects, the description is mostly sufficient. It could mention that returned operations are ordered by recency, or clarify 'operations' in the Stellar sense, but these are minor omissions that don't prevent correct invocation.

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 description coverage is 100%: both accountId and limit are described in the schema, including the default and range for limit. The description adds no extra meaning beyond the schema, so the baseline 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 uses a specific verb ('Get'), a clear resource ('operations'), and a scope ('recent... for a Stellar account'). It clearly states what the tool does. It doesn't explicitly contrast with sibling tools like getTransactions or getPayments, but 'operations' is a distinct Stellar resource, so the purpose is sufficiently clear.

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?

There is no guidance about when to use this tool versus its siblings. It doesn't mention that operations are distinct from transactions, payments, effects, or offers, nor does it specify any conditions that would make this tool the right choice. The context is implied but no alternatives or exclusions are given.

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