train_file

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

Describes key behaviors: tunnel-safe, image-only, size limit. No annotations, so description carries burden. Lacks details on error handling, authentication, or side effects, but covers essential constraints.

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, no fluff. Action first, then constraints. Efficient and well-structured.

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?

Covers purpose and constraints but doesn't specify return format (e.g., base64? binary? mime type?) or error behavior. With no output schema, this is a gap. Otherwise adequate for a simple fetch.

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?

Only one parameter (path) with schema description. Description adds value by specifying the path is absolute under training root and referencing sources (datasetPath or samples). Complements schema well.

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?

Clearly states it fetches an image under training root as inline image, with specific constraints (image only, ≤2MB). Distinguishes from sibling tools like get_image or view_image by focusing on training files and tunnel-safe access.

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?

Explicitly says it's for phone/panel to render files unreachable via /view, providing clear context when to use. Does not explicitly state when not to use, but constraints imply limitations.

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