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

With readOnlyHint=false declared, the description supplies exactly the missing context: resolving has a side effect (the name joins the tracked universe), that membership is conditional on room, and it can later be displaced. It also tells the agent where to look for the outcome ('watchlisted' in the result). It stops short of stating what happens on a non-resolving name or any capacity/auth constraints.

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?

Two sentences, front-loaded with the core action, and every clause carries information the agent cannot get from the schema or annotations. No filler or restatement of the title.

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 one-parameter tool with no output schema, the description covers the key return signal ('watchlisted') and the non-read-only side effect, which are the two things an agent most needs. It is only slightly incomplete on failure behavior for unresolvable names and on what 'the list' and 'room' mean concretely.

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% for the single 'query' parameter, so the schema already carries the semantics and the baseline is 3. The description restates 'ticker or company name' but omits the fragment/partial-match nuance that the schema's pattern and 'fragment' wording imply.

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 first sentence names a specific verb and resource ('Resolve a ticker or company name'), so an agent knows this is a symbol/ticker lookup rather than a data read. It does not explicitly contrast itself with the read_* siblings, but none of them overlap in function, so disambiguation is largely unnecessary.

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 explicit when-to-use or when-not-to-use guidance, and no named alternative such as read_watchlist or read_instrument_quotes for agents that already have an identifier. Usage is only implied by the word 'Resolve'; the disclosure about joining the tracked universe is behavioral, not prescriptive.

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