athena_bionano_assembly

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

With no annotations, the description carries the full burden. It adds some behavioral detail about preserving the BOM separately and differing from generic modules, but omits that this is a read-only operation, any side effects, authentication needs, or error behavior. The jargon further reduces confidence in understanding the tool's behavior.

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 brief but poorly structured. The second sentence is a run-on with unnecessary acronyms and convoluted phrasing, making it hard to parse. The key purpose is front-loaded, but the added detail earns no clarity points because it is more confusing than helpful.

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?

For a tool with one parameter, no output schema, and no annotations, the description is grossly insufficient. It does not explain what machine_id is, what an 'assembly/function packet' contains, or how to interpret the result. The agent cannot reliably invoke this tool correctly.

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 only parameter, machine_id, has no description in the schema (0% coverage). The tool description does not mention machine_id at all, leaving the agent to guess what values are valid or what the parameter signifies. The description fails to compensate for the schema gap.

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 states a clear action ('Return an assembly/function packet'), but the resource is vague and the subsequent jargon ('15-part USER_VISUAL BOM', 'primary-source-conditioned infection transition sequence') obscures what the tool actually does. It attempts to distinguish from siblings ('other machines return generic functional modules') but not effectively.

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?

No explicit guidance on when to use this tool versus alternatives. It contrasts with 'other machines' but does not name specific tools or provide decision criteria. The implication that this tool is for T4-specific packets is not directly actionable.

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