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

No annotations are provided, so the description carries the behavioral burden. It does convey that the tool returns a comprehensive machine card rather than a summary, and 'get' implies a read-only lookup. It does not discuss error behavior, authorization, or what happens when the id is invalid, but for a simple retrieval tool the stated behavior is reasonably clear.

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 a single, front-loaded sentence with no filler. It is appropriately brief for a one-parameter lookup tool, though slightly more context about usage would have made it more 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 simple get-by-id tool, the description and schema give an agent enough to call it. However, with no output schema and no mention of what fields constitute the 'full card', return expectations are left vague.

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 schema already documents the sole parameter as the machine's product_number, so the description adds little beyond restating that relationship. With 100% schema description coverage, the baseline of 3 is appropriate.

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 names the operation (retrieving the full machine card) and the lookup key (product_number/id). It distinguishes itself from list-style tools like search_machines by emphasizing 'full card', but it does not explicitly name any sibling it contrasts with.

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?

Usage is implied: call this when you need a complete machine record by product_number. However, there is no explicit guidance about when to prefer this over search_machines, compare_machines, or get_machine_images, and no exclusions or prerequisites are stated.

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