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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that the tool returns commercial fields and a BOM existence check, which is useful context. It does not describe any additional side effects or edge cases, but given the annotations, the bar is lower. No contradiction with annotations.

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 only two sentences, which is concise. However, the second sentence about the 'layer flag' is somewhat cryptic because the schema has no such parameter; it may confuse an agent. The core purpose is front-loaded, but the ambiguity detracts slightly from clarity. Overall, it is brief and to the point.

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 and no output schema, the description should at least explain the parameter and the return format. It does neither. The mention of a 'layer flag' that isn't in the schema is confusing. The description gives a high-level purpose but lacks essential details for correct invocation, such as how robot_id is used or what the response looks like. This is inadequate for an agent to confidently use the tool.

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 for the undocumented robot_id parameter. The description does not explain what robot_id is, its format, or how to obtain it. It only implies that you need to specify a robot. This is a significant gap for a tool with a single parameter, and the description provides no value beyond the schema itself.

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 the tool returns a commercial profile (specs, pricing, viability score) and whether a semiconductor BOM exists. It also hints at the difference between the three get_robot variants ('layer flag is the only difference'), which helps distinguish from mechanical_get_robot and software_get_robot. However, it does not explicitly name those siblings or mention other hardware-specific tools like hardware_get_robot_hardware.

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 implies that the only difference among the three get_robot variants is the layer, so an agent could infer which variant to use based on the desired layer (hardware/mechanical/software). It does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternative tools for other purposes (e.g., signals, block analysis). The guidance is implicit rather than direct.

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