billy_report_profit_loss

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'READ-ONLY' which indicates no mutation, but fails to describe the report's scope, data sources, date range interpretation, or what happens if parameters are missing or invalid.

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 extremely short (two fragments) but lacks structure and substantive content. Conciseness should not come at the expense of completeness; here it fails to provide adequate information for an agent to understand the tool's full behavior.

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 has three parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain what the report returns, how to interpret the date parameters, or how it differs from other report tools. This leaves the agent with insufficient information for correct invocation.

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 0%, yet the description adds no explanations for the three parameters (fromDate, toDate, accountGroupId). While fromDate and toDate are somewhat self-explanatory, accountGroupId is not described at all, and the description provides no format or usage details.

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 identifies the tool as generating a P&L (Profit and Loss) report, which is a standard financial report. The term 'P&L report' is specific and understandable. However, it does not differentiate this report from sibling report tools like billy_report_balance or billy_report_invoiced_sales.

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 provides no guidance on when to use this tool versus alternative report tools. It only states it is read-only, which is a general property but not usage context. There is no mention of prerequisites, typical use cases, 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.