get_single_manual_account

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

The readOnlyHint annotation already covers the safety profile, and the description aligns with it by saying 'get details.' The description adds the 'manual account' scoping but does not disclose response shape, error behavior, or other runtime traits beyond what the annotation and schema already imply.

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 a single efficient sentence that communicates the action, target, and discriminator with no wasted words.

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-only single-resource getter with one well-documented parameter and a readOnlyHint annotation, the description is largely complete. The only minor gap is that 'details' is slightly generic and could be more precise about what the response contains, but no output schema exists to fill that in.

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%, and the accountId parameter is already described as 'Id of the manual account to query' with discovery guidance. The tool description adds little beyond the schema, so baseline 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 details') and identifies the exact resource ('single manual account') plus the selection mechanism ('by ID'). This clearly distinguishes it from get_all_manual_accounts and the analogous get_single_plaid_account sibling.

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 parameter description explicitly instructs the agent to call get_all_manual_accounts first to discover IDs, providing practical usage guidance. It does not explicitly state when not to use this tool versus alternatives, but the 'single manual account by ID' scoping makes the intended use clear.

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