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

The readOnlyHint=false annotation already signals mutation, and the description adds only the word 'manual' without explaining consequences of adding, removing, or updating positions. It does not disclose whether existing manual entries are replaced, whether broker-synced positions can be affected, or whether changes are reversible. No contradiction exists, but the description does little to explain behavior beyond the annotation.

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, with no filler or repetition. It is front-loaded with the core action ('manual change') and resource ('portfolio positions'). However, the brevity borders on under-specification, so it does not earn the top score for structure.

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 tool with three distinct array operations, zero required parameters, no output schema, and no rich annotations, a single vague sentence is grossly inadequate. An agent cannot infer when to use add vs remove vs update, how manual and broker-synced positions interact, or what side effects will occur. The definition is far from complete for safe 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 only 33%, and the description adds no parameter-level meaning whatsoever. It does not explain what 'add', 'remove', or 'update' mean semantically, how manual entries differ from broker-synced entries, or what values like avgCostPLN represent. The schema provides some descriptions for remove and update, but the description itself fails to compensate for the low coverage.

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 a clear mutating intent: manual changes to portfolio positions. It conveys the resource (portfolio positions) and the general action (change) without being a tautology. However, it does not mention the three concrete operations (add, remove, update) that the schema exposes, and it does little to distinguish itself from sibling tools like modify_watchlist or set_cash_balance.

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?

There is no guidance about when to use this tool versus alternatives such as submit_broker_transactions or modify_watchlist. The word 'manual' implies it is for hand-entered positions rather than broker-synced ones, but this is only implied and never made explicit. No exclusions, prerequisites, or decision criteria are provided.

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