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 safety profile is covered. The description adds the useful context that the result is a set of tracked instruments with specific attributes, but it does not disclose edge behaviors such as what happens when the optional household_id is omitted.

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 compact sentence with no filler or repeated title content. It front-loads the core subject and lists the returned attributes efficiently, making it easy to scan.

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?

With an output schema present and rich annotations, the description does not need to explain return shapes or safety. Still, the tool has an optional household_id with a default of '', and the description does not clarify whether omitting it lists all households or a default household, which is a meaningful gap for correct invocation.

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?

The schema has 0% description coverage, so the description must carry weight. 'The household's tracked instruments' does imply that household_id scopes the listing, and the parameter name plus default make its role reasonably clear. However, the description does not explain expected format, default behavior when omitted, or any constraints, so it only partially compensates for the missing schema descriptions.

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 the resource ('household's tracked instruments') and the attributes returned ('price, momentum, how each leans and volatility'), so an agent can tell this is a watchlist-listing tool. It lacks an explicit verb, but the title supplies 'List,' and the content is clear. It does not explicitly differentiate from overlapping siblings such as get_market_data or run_technical_analysis, though the watchlist framing helps.

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 no guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or sibling tools like get_portfolio_positions, list_accounts, or run_technical_analysis, leaving the decision entirely to inference.

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