create_line_3d

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

No annotations provided, so description carries full burden. Discloses interactivity (WebGL, orbit-able) and return structure ({filepath, title, rows}). However, does not clarify side effects (e.g., file saving) or data handling beyond the return.

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?

Five sentences, well-structured, front-loaded with key information. No unnecessary words or redundancy.

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?

Describes purpose, ideal use, return value, and key behavior. Lacks details on parameter constraints (e.g., data must contain columns), but schema covers those. Good overall coverage for a tool with moderate complexity.

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%, so description adds marginal value. It clarifies that color_column splits points into separate lines, adding context beyond the schema's description. Adequate but not exceptional.

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 it creates an 'Interactive 3D line / trajectory chart' (specific verb and resource). It distinguishes from sibling 3D charts by emphasizing trajectory and splitting by color_column.

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?

Explicit ideal use cases are given (e.g., route through lat/lon/altitude, metric across region × time). Does not explicitly state when not to use or list alternatives, but the examples are clear and helpful.

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