engine_params

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

No annotations exist, so the description carries the full behavioral burden, and it says nothing about whether this reads or mutates state, what permissions it needs, or what shape the response takes. The only added signal is the 'shared wear formula' reference, which implies consistency with other tools but is unexplained.

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?

It is short, but the brevity comes from under-specification rather than efficiency: a single sentence fragment that omits the verb and the return semantics. There is nothing to trim, but nothing is front-loaded either because the core action is never stated.

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?

With no annotations, no output schema, and an untyped nested object parameter, the description must do all the work and does none of it. An agent cannot determine what this tool returns or how to populate 'spec' from this text alone.

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 0% for two required parameters, one of which ('spec') is a free-form nested object with additionalProperties=true and no documented keys at all. The description mentions 'variant' and 'slot' but never clarifies what belongs in 'spec', leaving the most complex parameter completely opaque.

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 is a noun phrase with no verb, so it never states what the tool actually does (retrieve? compute? list?). It names a resource ('a variant's values by slot for an engine material') but gives no contrast against siblings such as read_finish or check_finish, so an agent cannot tell which tool to reach for.

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?

There is no when-to-use, when-not-to-use, or alternative named anywhere. The phrase 'follows the shared wear formula' hints at a domain constraint but does not tell the agent under what conditions this tool applies versus the twelve sibling tools.

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