get_bizmoney

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

With no annotations provided, the description must convey behavioral aspects. It states the outputs but does not mention whether the operation is read-only, any authentication requirements, or data freshness. The description is functional but lacks depth in disclosing non-obvious behaviors.

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 exceptionally concise: two lines summarizing the core value followed by a compact list of example queries. Every sentence and example is purposeful, with no redundancy 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?

Given the lack of output schema and parameters, the description adequately covers the tool's purpose and typical questions. It does not specify output format or units, but for a simple query tool, the provided information is sufficient for an agent to understand and invoke it correctly.

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 input schema has zero parameters with 100% coverage, meaning no additional documentation is needed. According to guidance, 0 parameters warrants a baseline of 4. The description adds no parameter info, but none is required.

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 tool provides three specific outputs: bizmoney balance, recent 7-day consumption trend, and remaining days estimate based on current pace. This distinguishes it from sibling tools like get_performance_report or get_today_status, which focus on different aspects of ad account data.

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 includes a list of example questions that map directly to common use cases, such as checking balance or estimating remaining days. While it does not explicitly state when not to use the tool, the examples provide strong contextual guidance for the AI agent.

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