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

No annotations are provided, and the description does not reveal behavioral traits such as output format, return structure, pagination, or real-time limitations. It only says 'track' and 'monitor' without explaining what the response contains, leaving the agent with significant uncertainty.

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 extremely concise, consisting of two short sentences that directly convey the purpose without any redundant or extraneous information.

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 no output schema and no annotations, the description must fully explain the tool's behavior and returns, but it only vaguely mentions 'percentage and value changes over various time periods' without specifying the exact data structure, available periods, or how to interpret the results. This is insufficient for a tool with a single param and no structured schema.

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 only one parameter 'symbol' with a basic description 'Stock symbol', and the description adds no additional meaning about the symbol format or constraints. Since schema coverage is 100%, a neutral score is appropriate, but the description does not enhance parameter understanding.

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?

Description clearly states the tool tracks stock price fluctuations and monitors percentage and value changes over daily, weekly, monthly, and long-term periods. This specific verb+resource+scope distinguishes it from sibling tools like getQuote or getHistoricalChart.

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 implies the tool is used for monitoring price changes over various timeframes, but it does not explicitly state when to use this tool versus alternatives, nor does it mention any exclusions or preference conditions.

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