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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description carries little burden for safety disclosure. It adds useful context about the response fields (symbol, exchange, quantity, note), which helps the agent know what to expect. However, it does not disclose any behavioral traits like pagination, ordering, or rate limits, which could be relevant for a list-style read.

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 that front-loads the core output content. It avoids unnecessary words and is easy to parse. It could be slightly more informative, but it is appropriately sized for the tool's simplicity.

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?

Given the absence of an output schema, the description does explain the return fields, which is helpful. However, it lacks guidance on how to specify the collection or team, does not mention pagination or limits, and does not differentiate from sibling tools like collections.list. For a read operation with annotations covering safety, this is adequate but not complete.

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% (teamId has a description, collectionId and limit do not). The description does not compensate for this gap. It mentions 'one team collection' which hints at the teamId parameter, but it does not explain what collectionId refers to or how to obtain it, nor does it clarify the limit parameter. The schema already covers teamId, so the description adds minimal value beyond that.

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 what the tool returns ('Items in one team collection: symbol, exchange, quantity for portfolios, and the note on each item') and the title clarifies it reads a watchlist or portfolio. It clearly identifies the resource (collection items) and implies a read operation, but it does not explicitly use a verb like 'gets' or 'retrieves'. It is distinct from siblings like collections.list (which lists collections) because it specifies item-level fields, though it doesn't explicitly name the sibling.

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 provides no guidance on when to use this tool versus alternatives. It does not mention when to use collections.get over collections.list or collections.add_symbol, nor does it state any prerequisites or context (e.g., having a collectionId from collections.list). The title implies a read operation, but there is no explicit usage context or exclusions.

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