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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds minimal behavioral context ('Remove one item'), which is consistent with the annotations. It doesn't add details about side effects, permissions, or error handling, but given the annotation coverage, the description is acceptable and doesn't contradict annotations.

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 concise sentence with no fluff, which is appropriately short. However, it is so minimal that it sacrifices informativeness for brevity. It front-loads the action but doesn't provide enough substance to be fully useful.

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 4 parameters (2 required) and no output schema, the description is quite incomplete. It doesn't mention return values, error scenarios, or additional context like how to get collectionId or when exchange is needed. The annotations cover safety, but the description leaves many operational details unaddressed.

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 25% (only teamId has a description). The tool description does not explain any parameters, such as what collectionId refers to, the format of symbol, or the optionality of exchange. With low schema coverage, the description should compensate, but it doesn't, leaving agents to infer parameter meaning from names and context.

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 specific verb ('Remove') and a resource ('one item from a team collection'), which is clear and distinct from the sibling 'collections.add_symbol'. However, it doesn't explicitly mention 'symbol' or 'watchlist/portfolio' as in the title, so it's not fully precise, but the tool name and title provide the missing context. It adequately conveys the core action.

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 on when to use this tool versus alternatives. It doesn't mention prerequisites, when removal is appropriate, or contrast with 'collections.add_symbol' or other collection operations. An agent must infer usage solely from the name and title.

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