getStockPriceChange

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

Annotations already indicate read-only and idempotent behavior. The description adds context about real-time tracking and monitoring over time periods, but does not disclose limitations like supported symbols, data freshness, or what happens for invalid symbols. With strong annotations, the added value is moderate.

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 two sentences, front-loaded with the action verb 'Track'. It is concise but the second sentence slightly repeats the first. Overall efficient, but could be trimmed.

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 no output schema, the description hints at response contents (percentage and value changes over periods). For a simple one-parameter tool, this provides adequate context, though it could specify whether it returns a single value or multiple periods.

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?

Input schema has 100% coverage for the single required 'symbol' parameter with a basic description. The description does not add extra meaning about symbol format, case sensitivity, or examples. As schema coverage is high, baseline of 3 is appropriate.

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 tracks stock price changes (percentage and value) over various time periods, using a specific verb 'Track' and naming the FMP API. However, it does not contrast with sibling tools like getQuote or getIntradayChart, leaving some ambiguity about when to use this specific tool.

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?

No guidance is provided on when to use this tool versus alternatives such as getQuote (current price) or getIntradayChart (intraday data). The description lacks explicit when-to-use or when-not-to-use scenarios.

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