get_single_plaid_account

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

Annotations already declare readOnlyHint=true, and the description consistently indicates a read-only retrieval. The description adds mild context by clarifying the account is Plaid/synced, but does not disclose return format, error behavior, or permissions. No contradiction.

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, compact sentence with no filler. The key facts—action, resource, and identifier—are front-loaded and immediately usable.

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?

This is a simple one-parameter read-only lookup. The description plus schema fully cover what the agent needs to invoke the tool correctly, and the annotation covers the safety profile. No output schema is present, but 'details' is sufficient given the low complexity.

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%, so the parameter is already documented. The description adds value beyond the schema by including a discovery prerequisite ('Call get_all_plaid_accounts first'), which helps the agent obtain a valid accountId.

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 ('Get details'), a specific resource ('single Plaid (synced) account'), and the access method ('by ID'). This clearly distinguishes it from get_all_plaid_accounts and manual account tools.

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 itself does not name alternatives, but the parameter schema explicitly instructs the agent to call get_all_plaid_accounts first to discover account IDs. This provides clear when-to-use context, though it lacks explicit exclusions or alternative tool routing.

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