assembly_feeder_setup

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

No annotations provided. Description mentions optimization goal and caution, but does not detail side effects, permissions, or error conditions. Adequate for basic understanding.

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?

Three focused sentences. No wasted words. Key information front-loaded with 'Station 2' and core purpose.

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?

Output schema exists to document return structure. Description covers core function, sequential context, and a caution. Could mention expected output more explicitly, but sufficient.

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 has 100% coverage. Description mentions uploading BOM and position CSV, which maps to bom_path and position_path, but adds no additional meaning beyond 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?

Clearly states 'Generate optimal feeder slot assignment' using BOM and position CSV. Distinguishes from sibling assembly tools like assembly_readiness_check or assembly_reflow_profile by specifying a unique station and function.

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?

Provides context with 'Station 2' and prerequisite 'Review the feeder map before loading the machine.' Does not explicitly mention when not to use or alternatives, but the context is clear enough.

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