High-pressure pump info

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

No annotations are provided, so the description carries the burden. 'Structured data' implies a read-only retrieval and the domain list clarifies scope, but it does not explicitly state side-effect-free behavior, auth needs, or output shape.

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?

One front-loaded sentence lists the domains compactly. It is dense but every clause maps to a section, with no filler.

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 low-complexity getter with an enum section and no output schema, the description enumerates the available data domains well. It still leaves the default 'all' behavior and exact section mapping to the schema, but is broadly complete.

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 single section parameter is an enum with 0% schema description coverage. The description echoes many enum categories but omits 'all', the 60K/40K split, and exact enum names, so it only partially compensates.

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?

Names the exact pump model and says it returns structured data across listed domains, so the resource and verb are clear. It does not distinguish itself from siblings like machine_overview or get_drive_parameters, so not a 5.

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 sentence states when to use this versus machine_overview/search or when not to use it. The content list implies it is for pump reference data, but no explicit routing guidance is given.

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