profit_and_loss

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It does disclose a meaningful filter ('from posted journal items only'), which is useful. However, it does not mention the read-only nature explicitly, nor what the report returns (e.g., totals, net profit), which would be important for an agent.

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, concise sentence that front-loads the essential purpose. It contains no filler words and is highly 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?

With no output schema and no annotations, the description must explain what the tool returns. It specifies the data source (posted journal items) and account types (income/expense), but not the report structure or key output metrics (e.g., net income, totals). This leaves a significant gap for an agent interpreting the response.

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%, so the description must compensate for parameter meaning. It only mentions 'date range' which maps to date_from and date_to, but does not explain the date format or the purpose of company_id. This is insufficient given the lack of schema descriptions.

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 a Profit & Loss (income statement) for a date range, specifying that it covers income and expense accounts from posted journal items. This distinguishes it from sibling report tools like balance_sheet or trial_balance by clearly defining its scope and data source.

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 when an income statement report is needed, and the 'posted journal items only' note warns against using this for draft entry analysis. However, it does not explicitly compare to alternatives like balance_sheet or general_ledger, leaving some ambiguity about when to choose this over those tools.

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