getHistoricalStockGrades

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered structurally. The description adds nothing behavioral beyond that: no ordering, no pagination behavior, no statement of how far back history goes, no mention that limit defaults to 100 and caps at 1000.

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?

Only two sentences, but one is filler branding ('with the FMP Historical Grades API') and the other leans on marketing phrasing ('comprehensive record'). The useful substance could fit in a single clause.

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?

No output schema exists, and the description does not say what a grade record contains (firm, action, previous/new grade, date), how results are ordered, or how far back the history reaches. For a historical-data tool this leaves the agent unable to predict the result shape.

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 both parameters (symbol, limit) are documented in the schema already. The description adds no format or scope detail beyond implying symbol-based lookup, so the baseline 3 applies.

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?

States a specific verb+resource: retrieving historical analyst grades for a stock symbol. However, it does not distinguish this from close siblings like getStockGrades, getHistoricalRatings, or getStockGradeSummary, so an agent still has to guess which 'grades' tool is right.

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 when-to-use or when-not-to-use guidance at all. It never mentions getStockGrades (current grades?) or getHistoricalRatings, both of which sit right next to it in the sibling list, leaving selection ambiguous.

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