lemma_get_external_account

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

With no annotations provided, the description carries the behavioral disclosure burden. It communicates that the tool is read-only by using 'Get' and indicates what data is returned, but it does not describe not-found behavior, authentication requirements, or any peculiarities of the response. For a simple getter this is adequate but not rich.

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, front-loaded sentence that states the action, target, identifier, and representative return fields without any filler. Every word contributes to the agent's understanding.

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 one-parameter getter with no output schema, the description covers the resource, the lookup key, and expected response fields. It is nearly complete, though it could briefly note the relationship to list_external_accounts or clarify that only one record will be returned.

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 0%, so the description must compensate. It adds that the ID identifies a saved recipient, but provides no format, source, or elaboration beyond the parameter name external_account_id, which is already fairly self-explanatory.

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 specifies a clear verb ('Get'), resource ('one saved recipient'), and access method ('by ID'), and lists the key returned fields. It is clearly distinguishable from the sibling list_external_accounts tool, which would be the plural/batch alternative.

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 phrase 'one saved recipient by ID' implies this tool is for single-record retrieval when an external_account_id is available. It does not explicitly name list_external_accounts as the alternative for fetching all recipients, but the singular/plural contrast provides clear context.

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