snb_get_banking_income

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

Annotations already indicate readOnly, destructive, and idempotent hints. The description adds that values are in millions of CHF and returns both markdown and JSON, providing useful behavioral context beyond annotations.

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 concise (6 lines), front-loaded with a clear summary, and uses a well-organized 'Args' section. No unnecessary content.

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 tool's complexity (1 nested parameter), annotations, and output schema existence, the description provides sufficient context: return format (markdown+JSON), unit conversion, and reference to sibling tool for bank groups. Minor gap: no mention of date range defaults beyond schema.

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 detailed parameter descriptions (e.g., bank_groups default, year format), and the description summarizes the args and notes default behavior. Together they cover semantics well, with the description adding overall return format.

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 uses specific verbs ('Retrieve') and resources ('banking income statement data from SNB Warehouse (BSTA EFR cubes)'), clearly distinguishing it from sibling tools like snb_get_balance_sheet.

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 implies usage for retrieving income statement data and mentions default bank groups, but does not provide explicit when/why to use this tool versus alternatives or when not to use it.

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