sc_overnight

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

Without annotations, the description clearly discloses the auto-resolution behavior, which is a key behavioral trait. It does not mention any destructive effects, authentication needs, or rate limits—but none are expected for a read-only summary tool, so the disclosure is adequate.

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: two sentences, zero filler. The first sentence states the core purpose, and the second sentence adds a critical behavioral clarification. Every word earns its place.

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?

Given that the tool has only one optional parameter and an output schema exists, the description is nearly complete. It covers purpose, auto-resolution behavior, and expected return data. A minor gap is not explaining the output schema's structure, but that's mitigated by the schema itself.

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 should compensate. The description mentions that an account ID can be omitted for auto-resolution, which adds meaning beyond the schema's nullable optional parameter. However, it does not explain how to find the ID if needed, leaving the parameter semantics partially underdefined.

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 verb 'Get', the resource 'Scalable Capital overnight savings account summary', and the specific data returned ('balance and interest rate'). It also includes an automatic resolution behavior that distinguishes it from siblings.

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 explicitly mentions that the account is auto-resolved when exactly one active account is accessible, which helps the agent understand when no parameter is needed. However, it does not explicitly describe when not to use this tool or mention alternatives among siblings.

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