direct_account_balance

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

With no annotations, the description must carry the burden. It does declare 'READ:' to signal a non-mutating operation, and 'snapshot' implies a point-in-time view. However, it does not disclose the exact account format, limitations of the sample, or any requirements, so transparency is minimal.

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 efficiently conveys the read operation and the target data. No redundant words or filler.

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?

The tool is simple (zero params, no output schema). The description gives a reasonable purpose but lacks any mention of response shape or relationship to other account-level tools. Given the system does not provide annotations or an output schema, the description should offer more context for the agent, though it is sufficient for a minimal read operation.

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 tool accepts zero parameters, so schema description coverage is trivially 100%. Per the rubric, a zero-parameter tool gets a baseline of 4; the description correctly omits parameter details.

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 opens with 'READ:' and specifies the exact resources (client financial flags, campaign Funds/SharedAccountFunds), with 'cabinet balance snapshot' clarifying the output kind. It distinguishes the purpose from siblings like direct_list_campaign_funds by combining financial flags with a balance snapshot, though the phrase 'sample' is slightly ambiguous.

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?

No guidance is provided on when this tool should be chosen over siblings such as direct_account_summary or direct_list_campaign_funds. The description only states what it does, leaving the agent to infer the use case.

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