get_expense_distribution_report

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'returns' a report, which implies a read operation, but does not confirm side effects, auth requirements, rate limits, or output format. The lack of output schema further compounds this gap.

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 sentence, which is concise. However, it lacks structure and does not front-load critical information. The conciseness comes at the cost of completeness, making it minimally viable.

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 (7 parameters, nested objects, no output schema, 46 siblings), the description is severely incomplete. It does not explain the report's content, return format, or how filters affect results. The agent cannot reliably invoke this tool without additional context.

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 only 29% (only two date parameters have descriptions). The description mentions 'given filters' but does not explain the meaning or usage of the 7 parameters, including nested objects like 'properties' and 'party_contact_info'. The agent has insufficient information to populate parameters correctly.

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 it returns an 'expense distribution report' but does not specify what this report contains or how it differs from the 46 sibling report tools. The name suggests a specific financial report, but without further clarification, the agent cannot distinguish it from similar reports like 'get_account_totals_report' or 'get_budget_comparative_report'.

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 on when to use this tool versus alternatives. The description does not mention any prerequisites, typical use cases, or conditions under which this report is appropriate. Without this, an agent may select the wrong tool.

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