getPriceTargetConsensus

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds value by naming the output measures (high/low/median/consensus), which matters because there is no output schema, but it adds nothing about freshness, coverage, or how consensus is computed, and the second sentence is marketing framing rather than behavioral information.

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, front-loaded with the useful content. The clause 'with the FMP Price Target Consensus API' is redundant with the name, and 'offering investors a comprehensive view of market expectations for future stock prices' is filler that does not help an agent decide or invoke.

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 single-parameter read tool with full annotation coverage, the definition is minimally sufficient and does disclose the returned fields. It is still missing the one thing an agent in a large price-target tool cluster needs: how this endpoint differs from the summary and news siblings.

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?

There is a single parameter with 100% schema description coverage ('Stock symbol'), so the schema carries the semantics. The description does not clarify symbol format, exchange prefixes, or whether the symbol must be a live equity, so it adds nothing beyond the schema. 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 and resource ('Access analysts' consensus price targets') and enumerates the returned measures (high, low, median, consensus). However, it never distinguishes itself from close siblings such as getPriceTargetSummary or getPriceTargetSummariesBulk, so an agent must infer the boundary.

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 gives no when-to-use guidance, no prerequisites, and no mention of alternatives like the summary or bulk price-target tools. The agent is left to guess which of the several price-target endpoints is appropriate.

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