ozon_finance_mutual_settlement

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. The word 'report' implies a read/retrieval operation, but the description does not state what data is returned, whether it is read-only, or any limitations. This is minimal behavioral context.

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 focused phrase with no filler and is perfectly sized for a one-parameter tool. It front-loads the core resource ('monthly mutual settlement report') without unnecessary elaboration.

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 annotations and no output schema, the description leaves important gaps: it does not explain what the report contains, how it differs from other finance siblings, or what the agent should expect as a result. The tool is simple, but the description is still too thin to fully support correct selection and 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?

The schema already documents the only parameter, date, with format YYYY-MM, so schema coverage is 100%. The description adds 'monthly' context but does not meaningfully expand on what the date parameter means beyond the schema. Baseline 3 applies because the schema does the heavy lifting.

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 identifies a clear resource: a monthly mutual settlement report. It lacks an explicit verb like 'get' or 'list', but the noun phrase 'report' makes the intent reasonably clear. It does not name or distinguish itself from sibling finance tools.

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 alternatives such as ozon_finance_transactions, ozon_finance_totals, or ozon_finance_balance. The context of 'mutual settlement' is implied by the name and description, but no when-to-use or when-not-to-use information is given.

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