get_book_summary

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

The description discloses that the tool operates on the 'entire' book (not a filtered subset), returns a single text response rather than structured data, and covers specific data categories. This gives useful behavioral context beyond a bare tool name, though there are no annotations to supplement.

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?

Two short paragraphs with zero waste. The first sentence states the purpose, the second enumerates content, and the final sentence gives usage guidance. Every sentence earns its place and it is extremely efficient.

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 read-only overview tool with 0 parameters, no annotations, and clear output expectations, the description is complete. It explains what's included, how results are returned (single text response), and when to use it. Nothing material is missing for an agent to 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 tool has 0 parameters, so the description's job here is minimal — there's nothing to clarify beyond what the schema shows. The baseline for 0-param tools is 4, and the description adds value by confirming the tool is intended to be a self-contained orientation call with no inputs needed.

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 returns a compact overview of an entire GnuCash book, listing the specific fields included (path, currency, account structure, transaction counts, balances, net worth, commodities, scheduled transactions). This is specific verb+resource with a distinct scope that separates it from sibling report tools.

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?

Explicitly instructs 'Use this first to orient yourself,' which provides clear when-to-use guidance. This orients the agent to call this tool before diving into specific queries, differentiating it from the many sibling get_* and report tools.

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