getStockGradeNews

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

Annotations already indicate readOnly, idempotent, and openWorld hints. The description adds context about real-time updates and news links, which is helpful but not critical behavioral disclosure beyond annotations.

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?

Two sentences are concise and front-loaded with purpose. The second sentence is slightly long but contains relevant details. No wasted words.

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 the simple 3-parameter schema and rich annotations, the description adequately covers the tool's output (grades, news links, stock prices) and usage context. Missing explicit pagination info but acceptable.

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?

All three parameters (symbol, page, limit) have descriptions in the schema (100% coverage). The description does not add significant new meaning beyond confirming usage for specific symbols, so baseline score 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 provides real-time analyst grade changes with details like grading company, previous/new grades, and action. It distinguishes itself from siblings like getStockGrades and getStockGradeSummary by emphasizing real-time updates and news links, but doesn't explicitly differentiate.

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 usage for staying informed on analyst grade changes for specific symbols, but no explicit when-to-use, when-not-to-use, or alternatives provided. Lacks guidance on choosing this over sibling tools.

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