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

Annotations only provide readOnlyHint: false, which implies this is a write operation. The description says 'upload transaction history' but does not disclose whether it overwrites existing transactions, deduplicates by externalId, requires authentication, or has side effects on tax/settlement calculations. With minimal annotation coverage, the description carries the burden and fails to explain the behavioral traits.

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 short sentence, so it is concise, but it is under-specified. It is front-loaded in the sense that it is short, but it does not earn its place by adding enough value. A 3 reflects that it is not verbose but also not informative.

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?

For a write tool with three required parameters, no output schema, and no parameter descriptions, the description is incomplete. An agent cannot tell what response to expect, whether the operation is idempotent, or how the transaction history will be used. The complexity of the nested transactions array makes the lack of guidance more damaging.

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 the three required parameters. It does not explain what 'broker' and 'account' refer to (identifiers? names?), nor the format or constraints of 'transactions'. The nested transaction object has some inline descriptions (source, notes), but the top-level parameters are undocumented. The description adds no parameter-level meaning.

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 is in Polish: 'Wgranie historii transakcji do rozliczeń i podatków' translates to 'Upload transaction history to settlements and taxes.' It states a verb and resource, but it is vague about what 'submit' actually does (does it create, import, or replace records?). It does not distinguish itself from siblings like submit_portfolio_snapshot or get_transaction_history, and the name 'submit_broker_transactions' is only slightly expanded by the description.

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 given about when to use this tool versus alternatives. There is no mention of prerequisites, such as whether the broker/account must already exist, whether this is for importing historical data only, or whether it should be used instead of manual entry. The description implies a data-import use case but provides no explicit context or exclusions.

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