search_gl_balances

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

No annotations are provided, so the description must disclose behavior. It falsely claims 'ALL parameters are REQUIRED by the Oracle API', contradicting the input schema where only 4 of 7 are required. It fails to explain defaults, pagination, or any side effects.

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 very short (two sentences), which is concise. However, the second sentence is inaccurate, reducing effectiveness. It front-loads the purpose but fails to provide accurate details.

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 7 parameters, no output schema, and no annotations, the description is severely incomplete. It omits return value format, error conditions, and proper parameter guidance. The false requirement statement adds confusion.

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 57%, but the description adds no value beyond the schema. It repeats that parameters are required (incorrectly) and does not explain 'mode', 'limit', or 'offset'. The schema's own descriptions are minimal.

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 states 'Get GL account balances' which is a clear verb and resource. However, it does not differentiate from siblings, and the misleading claim that all parameters are required detracts from clarity. The tool appears unique among siblings, but the inaccuracy reduces the score.

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 to use this tool versus alternatives, nor any prerequisites or exclusions. The description simply restates the function without usage context.

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