Get Price Target

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

The description explains the default behavior (consensus split-adjusted average) and the effect of the list parameter. Annotations declare readOnlyHint=true, which aligns. No contradictions. It adds context 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 with no wasted words. Front-loaded with purpose. Efficiently conveys key information.

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 output schema exists and schema coverage is complete, the description sufficiently covers behavior. Could briefly mention prerequisites like data availability, but overall complete for a read-only analytics tool.

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 coverage is 100%, baseline 3. The description adds meaning by explaining the list parameter's effect (consensus vs per-analyst) and limit parameter's context (only when list=true). This goes beyond the schema.

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 gets analyst price target data for a ticker, distinguishing between consensus and per-analyst list. It uses specific verbs ('Get') and specifies the resource ('price target data'), differentiating it from sibling tools like get_analyst_consensus or get_analyst_estimates.

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 retrieving price targets but does not explicitly state when to use this tool versus alternatives like get_analyst_consensus. It provides context on the list parameter but lacks exclusions or comparisons to siblings.

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