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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), and the description adds genuinely new context: only manual records are editable while brokerage and imported records stay read-only, which matters for downstream calls. It omits any note about result size, pagination ceilings (limit max 100, offset max 2000), or ordering.

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?

Three short sentences, each doing distinct work: what is returned, what is editable, and when to call it. The purpose is front-loaded and nothing is redundant.

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?

An output schema exists, so return values need no explanation, and the editability note is a useful addition. However, for a paginated list tool with three undocumented parameters, the definition leaves the agent without guidance on paging or filtering, which is a material gap.

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 carries the full burden for limit, offset, and portfolio_name, yet it explains none of them. It alludes to "portfolios" plural, hinting portfolio_name may narrow the scope, but pagination behavior and defaults are entirely undocumented.

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 uses a specific verb and resource ("List transaction IDs and exact position records in the signed-in user's portfolios") and clarifies scope as the signed-in user's own data. It does not explicitly contrast with siblings like get_my_portfolio or edit_my_portfolio_transaction, so differentiation is left partly implicit.

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?

"Use this before selecting a transaction to change or remove" gives a concrete when-to-use condition tied to the edit/remove siblings. It also implicitly excludes brokerage and imported records from any follow-up edit, though it never states when-not to call this tool or what alternative lists exist.

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