getPriceTargetSummary

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. The description adds context about providing average price targets across timeframes, but does not elaborate on data freshness, limitations, or what 'summary' entails beyond the surface.

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, but the first sentence is verbose ('Gain insights into analysts' expectations for stock prices with the FMP Price Target Summary API'). It could be more concise without losing meaning.

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 explains the purpose and output type (average price targets from analysts). However, it could mention the exact output format or what 'summary' includes.

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 parameter 'symbol' is documented in the schema with 'Stock symbol'. The description adds no additional meaning, and with 100% schema coverage, the 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 'average price targets from analysts across various timeframes', which is specific and distinct from sibling tools like getPriceTargetConsensus or getPriceTargetLatestNews. It identifies the resource (price target summary) and the action (gaining insights).

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 assessing stock performance based on analyst expectations, but does not explicitly distinguish when to use this tool over siblings like getPriceTargetConsensus. No when-not-to-use or alternative guidance is provided.

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