Get Instances By Id

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

Annotations already declare this as a safe, idempotent read. The description adds valuable domain context beyond annotations, especially that `development` simulates settlement while `production` moves real funds, and that `onboarding_step=completed` means the instance can transact.

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 three short sentences with no filler. The core purpose is front-loaded, followed by the most important safety and onboarding context.

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 read operation with rich safety annotations and no output schema, the description provides enough behavioral context to interpret key fields safely. The main remaining gap is the unexplained `id` parameter.

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 has 0% description coverage for the single required `id` parameter, and the description does not explain what `id` represents, its expected format, or how it relates to the bound instance. It leaves the only parameter semantically undocumented.

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 states a specific action and resource: it returns the instance tied to the API key or connection. It is clear enough to distinguish this as an instance lookup tool, though it does not explicitly reinforce the `id`-based selection from the tool name.

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 gives useful conditional guidance to check `type` before moving money and explains what `onboarding_step` means. However, it does not explicitly say when to use this tool versus sibling instance or onboarding tools.

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