adjust_machine_parameters

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

With no annotations provided, the description carries the full burden. It adds a useful internal behavior ('Fetches current recipe internally from the database') and implies a mutation, but does not disclose side effects, reversibility, safety considerations, or prerequisites. This is adequate but not comprehensive.

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 extremely concise: two sentences front-loading the main action, then adding one valuable internal detail. Every word earns its place, with no redundant or vague phrasing.

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?

This tool performs a potentially impactful adjustment and has no annotations or output schema. The description explains the core purpose but omits parameter semantics, expected return values, failure modes, permissions, and any warnings about the mutation. Given the tool's complexity, this is insufficient for full autonomous invocation.

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 description coverage is 0%, so the description must compensate by explaining parameters. It does not mention machine_id or defect_data at all. The only weak hint is 'dimension oversize' which loosely maps to defect_data.dimension, but there is no real semantic guidance.

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 a specific action (calculates and adjusts) on a specific resource (machine tool offsets) with a clear purpose (to fix quality defects like dimension oversize). It is unambiguous and easily distinguishes this tool from its unrelated siblings.

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 provides clear usage context: use when a quality defect such as dimension oversize exists. It lacks explicit exclusions or alternative-tool references, but the sibling tools are sufficiently different that this is not a significant gap.

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