getQuote

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

Annotations already indicate readOnlyHint=true and idempotentHint=true, so the tool is known to be safe. The description adds that it returns 'up-to-the-minute prices, changes, and volume data', but it does not elaborate on update frequency, rate limits, or any side effects. This adds moderate value 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?

The description is two sentences long, directly stating the purpose and data returned. Every word adds value; there is no redundancy or fluff.

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?

For a simple tool with one parameter and no output schema, the description adequately covers what the tool does and what it returns. It could be slightly more explicit about the return fields, but given the low complexity, it is largely complete.

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?

With 100% schema description coverage (the parameter 'symbol' is described as 'Stock symbol'), the baseline is 3. The description reinforces that the tool works for 'individual stocks', adding slight context, but does not provide format examples or additional constraints.

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 'real-time stock quotes' and lists the data provided ('prices, changes, and volume'), with a specific verb 'Access' and resource 'stock quotes'. It distinguishes from sibling tools like getQuoteShort and getAftermarketQuote by specifying 'individual stocks' and referencing the FMP API.

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 given on when to use this tool vs alternatives such as getQuoteShort, getBatchQuotes, or getAftermarketQuote. The description does not mention any prerequisites, limitations, or scenarios where this tool is preferred.

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