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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, but the description adds critical context beyond them: the action 'cannot be undone' and 'Always confirm with the user before removing stocks.' It also clarifies that removal is 'entirely' (not partial), which helps the agent avoid a destructive mistake.

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 definition is front-loaded with the core action, followed by tightly scoped use cases, a safety warning, and an alternative-tool routing note. Every sentence earns its place; no redundancy or filler.

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 destructive, single-parameter mutation tool with no output schema, the description covers purpose, invocation scenarios, safety confirmation, irreversibility, and the correct sibling alternative. Nothing an agent needs in order to call it safely and correctly is missing.

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 100%, and the single 'symbols' parameter is already documented in the schema with an example array. The description reinforces the multi-symbol nature through use cases but adds no syntax, format, or constraint details beyond what the schema provides, so the baseline of 3 applies.

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?

States a specific verb ('Remove') and resource ('stocks from the user's portfolio entirely'), making the scope unambiguous. It explicitly distinguishes itself from the sibling 'update_portfolio_stock' for partial sells and references 'get_user_portfolio' as the source for symbol lookup.

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?

Provides three concrete use cases (single delete, bulk thematic delete, clear portfolio) and an explicit exclusion: 'For partial sells (reducing quantity), use update_portfolio_stock instead.' The confirmation requirement is also stated as a workflow rule, leaving no ambiguity about when and how to invoke it.

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