livefpl_transfer_trend_by_position

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

With no annotations, the description carries the full burden. It discloses that it produces a PNG image, describes visual encoding (circle size = volume, color = net direction, arrows), and explains the output structure (four panels). It stops short of stating side effects or read-only status, but for a render tool that is transparent enough.

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 well-structured: a one-line summary, a clear explanation of the visual output, and a dedicated Args/Returns section. It is front-loaded with the primary purpose and every sentence contributes to understanding the tool, with no filler.

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?

The tool is simple (one optional parameter, no output schema, no annotations) and the description fully covers what an agent needs: the purpose, the output format (PNG image with four panels), and the parameter semantics including a usage hint. Nothing essential is missing.

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 schema only defines 'top_n' as an integer with default 40, giving no semantic meaning. The description explains it as 'Number of highest-volume transfer pairs to consider' and adds a practical recommendation ('A larger value than the single-graph tool is recommended...'), which adds real value 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 opening sentence states a specific verb ('Render') and a specific resource ('transfer-trend graphs split by position as a 2x2 grid IMAGE'), and the rest details the output format. It clearly differentiates from siblings like livefpl_transfer_trend_graph by emphasizing the position-split aspect.

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 clear context: it renders position-specific graphs, and it even references the 'single-graph tool' when recommending a larger top_n. However, it does not explicitly name alternatives or state when NOT to use this tool (e.g., when you need the overall trend), though the positional split is strongly implied.

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