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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so 'Changes nothing' is largely redundant. However, the description adds genuine negative-space disclosure the annotations don't cover: no quantities, costs or notes exist on these records, which prevents an agent from calling this expecting holdings data.

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?

Four short sentences, front-loaded with the action and scope, with no filler. The trailing 'Changes nothing' is the one sentence that mostly duplicates the readOnly annotation rather than adding information.

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?

A parameterless, non-destructive list tool with no output schema: the description covers scope (the member's watchlist), the returned fields, the linked downstream constraint (research targets), and the fact that writes/pricing data are absent. Nothing an agent needs in order to call it 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?

Zero parameters, so the baseline is 4. The description usefully reallocates that space to describing the returned record shape (assetId, symbol, name, asset class, kind), which is the only payload documentation available since there is no output schema.

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?

A specific verb plus resource ('Lists the assets on the member's AstraEye watchlist') and it enumerates the returned fields. It is clearly distinguishable from add_to_watchlist / remove_from_watchlist / find_assets by naming the watchlist as the scoped collection.

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?

'Research runs only on watchlist assets' implies why an agent would call this (to discover what research can target), but it never states when to prefer this over find_assets or how it relates to the research-project tools. Usage is inferable rather than explicit, and no exclusions are given.

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