get_pnf

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It shares a scope limit (50 tickers) and the input format, but it never states whether this is a pure read-only lookup, what the response shape is beyond schema knowledge, or how errors/limit violations behave.

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-load the core capability and then state the essential input rule. Every word adds information; no fluff. A slightly richer context about output or alternatives could add more, but the text is compact.

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?

With only one parameter, an output schema present, and the input syntax + limit stated, there are enough operational details for a basic call. The main missing piece is sibling differentiation, though that is more a usage guidance concern than a completeness one.

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 0%, and with a single bare string parameter the description adds critical meaning: comma-separated tickers and a 50-ticker maximum. This bridges a serious gap in the input schema and gives an agent the format it needs for a successful call.

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 names a specific resource (Point & Figure signal, breakout pattern, relative strength vs SPY) and the target tickers, so an agent can tell it apart from siblings like get_stage or get_macro without opening the schema. It does not explicitly name any sibling, but the substantive content is enough to identify its purpose.

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 text provides practical usage details: hold up to 50 tickers and pass them as a comma-separated string. It gives no when-to-use-versus-alternatives guidance or exclusions, so it leans on the agent to infer when P&F analysis is the right choice relative to siblings.

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