clear_account_override_tool

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

With no annotations, the description carries the burden of explaining behavioral impact. It states the removal action but does not mention whether the operation is irreversible, requires special permissions, or affects account data beyond the APR override.

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 extremely concise, containing only two short sentences with no redundant information. The core action and a platform qualifier are presented efficiently.

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 single-parameter mutating tool with no output schema, the description covers the essential purpose and platform scope. It lacks behavioral detail, but the overall context is reasonably complete.

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 only provides 'account_id' as a required string with no description. The description ties the parameter loosely to 'an account' but does not clarify the expected ID format, scope, or whether it refers to a Plaid account ID.

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 clearly states the action ('Remove any APR override') and the target ('for an account'), distinguishing it from related tools like set_account_override_tool and list_overrides_tool.

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 'Plaid-only' note provides a platform restriction, but there is no explicit guidance on when to use this tool versus setting or listing overrides. Usage must be inferred from the tool name and sibling context.

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