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

Annotations already cover read-only, destructive, and idempotent hints. The description adds valuable behavioral context beyond annotations: it clarifies that quantity applies only to portfolios and that the note is a label, not research. It also implies an upsert behavior ('Add or update'), which is consistent with idempotentHint=true. No contradictions found.

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 three short sentences with no filler. Each sentence adds value: the action, the quantity constraint, and the note clarification. It is front-loaded with the core action and immediately provides the most important usage nuances.

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 simple mutation tool with annotations covering idempotency and safety, the description covers the essential usage context: what it does, key parameter nuances, and the upsert behavior. It does not mention return values, but the absence of an output schema makes that less critical. Overall, an agent can correctly invoke this tool based on the provided information.

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 17% (only teamId has a description). The description partially compensates by explaining the semantics of quantity and note, but it does not clarify symbol, exchange, or collectionId beyond their obvious names. Given the low schema coverage, more param clarification would be helpful, but the existing clarifications are useful.

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?

Description clearly states the action: 'Add or update one item in a team collection.' This identifies the verb (add/update), the resource (team collection), and differentiates from sibling tools like collections.remove_symbol. The title and description align, and the note about quantity applying only to portfolios further clarifies scope.

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?

The description gives clear context on when to use the tool (adding or updating a symbol in a collection) and clarifies specific usage nuances (quantity only for portfolios, note is a short label). It does not explicitly mention alternatives like remove_symbol for the opposite operation, but the purpose is unambiguous enough for an agent to select it appropriately.

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