get_broker_income_expenditure

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Get' implies a read operation, but lacks details on permissions, rate limits, data freshness, or output format. For a tool with zero annotation coverage, this minimal description fails to provide necessary behavioral context for safe and effective use.

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, clear sentence with no wasted words. It is front-loaded and efficiently conveys the core purpose without unnecessary elaboration, making it easy to parse and understand quickly.

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 complexity of financial data and lack of annotations or output schema, the description is insufficient. It does not explain what 'overview' includes, how data is returned, or any behavioral traits. For a tool in a domain with many siblings, more context is needed to ensure the agent can use it correctly without guesswork.

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 0 parameters with 100% coverage, meaning no parameters are documented in the schema. The description does not mention any parameters, which is appropriate since none exist. However, it could hint at implicit filtering (e.g., by broker or date), but given the schema's completeness, a baseline of 4 is warranted as it aligns with the lack of parameters.

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 'Get income and expenditure overview for brokers' clearly states the verb ('Get') and resource ('income and expenditure overview for brokers'), providing a basic purpose. However, it lacks specificity about what 'overview' entails (e.g., aggregated data, time period, format) and does not distinguish it from sibling tools like 'get_broker_monthly_statements' or 'get_broker_basic_info', leaving ambiguity about scope and differentiation.

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. With many sibling tools related to brokers (e.g., 'get_broker_monthly_statements', 'get_broker_basic_info'), the description offers no context on prerequisites, timing, or comparative use cases, leaving the agent to infer usage without explicit direction.

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