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

Annotations already declare readOnlyHint=true and idempotentHint=true, so repeating 'This is read-only' adds little. However, the description adds useful behavioral context beyond annotations: it discloses that the default folder's ID is included and that an ID must be chosen before writing to a non-default folder.

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, front-loads the core action and scope, and contains no filler. Every sentence contributes either purpose, read-only behavior, or the write prerequisite.

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 zero parameters, rich annotations, and an output schema, the definition is complete enough for an agent to call it correctly. It covers scope, read-only behavior, and the key prerequisite for using the returned ID in writes.

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?

This tool has zero parameters, so there is no parameter semantics burden. The description appropriately does not discuss parameters. Baseline 4 applies for a 0-parameter tool.

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 and resource: list the authenticated user's ValuEdge Watchlist folders, including the default folder ID. It is clear what the tool does, though it does not explicitly distinguish itself from get_my_watchlist or create_my_watchlist beyond the word 'folders'.

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?

It provides clear usage context: choose an ID before writing to a non-default folder. That tells an agent when the tool is needed in a write flow. It does not explicitly state when not to use it or name sibling alternatives, which keeps it from a 5.

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