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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is well-covered. The description adds value by disclosing 'No authentication required' and 'data is derived from most recent nightly analysis run' — useful behavioral context about data freshness and access requirements that annotations don't capture.

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 compact 4-sentence block that front-loads the core purpose, lists key outputs, discloses data freshness and auth, and ends with a direct usage recommendation. Every sentence contributes value with no waste.

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?

The tool has a rich output schema and annotations, so structural details are covered elsewhere. The description provides the key remaining context: data source freshness (nightly run), no-auth requirement, and an explicit use case for quick assessment. Minor gap: it doesn't explain what 'full analysis' means or reference the sibling initiate_analysis directly, though the usage guidance implies this relationship.

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%, so the schema already documents both parameters (ticker and exchange) well. The description adds no new parameter-level detail, which is acceptable given the schema coverage. Baseline 3 is appropriate since the schema handles the parameter documentation burden.

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 clearly states the tool retrieves a StockLens composite analysis summary with specific verb ('retrieve'), resource ('composite analysis summary'), and output details (composite score, rating, per-domain scores, strengths/challenges). This distinguishes it from siblings like get_portfolio_insights and initiate_analysis, which serve different purposes.

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 explicitly directs when to use this tool: 'Use this to quickly assess a stock before deciding whether to run a full analysis.' This creates a clear usage path and implies when NOT to use it (when a full/detailed analysis is needed). It also clarifies the data is from the most recent nightly run, setting expectations about freshness.

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