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

With no annotations, the description carries the full burden of disclosure, but it says nothing about side effects, read-only guarantees, or whether external systems are contacted. It only describes the content of the connections, not the behavior of the operation.

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 concise and packs relevant details into a single sentence. However, it begins with 'Linked' as a dangling modifier, which slightly hampers readability, and front-loads the action less effectively than starting with 'Lists' or 'Returns'.

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 simple list operation with no parameters and no output schema, the description covers the essential aspects: the type of connections returned and the included attributes (sync mode, last sync). While details like ordering or pagination are absent, nothing critical is missing for invoking this tool.

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 tool has zero parameters, so no parameter explanation is needed. The description correctly avoids adding parameter details, matching the baseline of 4 for parametric simplicity.

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 identifies the resource (exchange, bank, wallet connections) and key attributes (sync mode, last sync), which makes the tool's purpose fairly clear. However, the absence of an explicit verb like 'list' or 'returns' makes it a fragment, and it relies on the tool name to anchor the action.

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 provides no guidance on when to use this tool versus siblings like 'sync_connections' or 'list_transactions'. There is no mention of alternatives, exclusions, or context in which this tool should be preferred.

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