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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds a genuinely non-obvious trait: the operation is all-or-nothing on authorization — one missing right causes a refusal naming the robot and no comparison at all. That failure mode is not derivable from the schema or annotations. It could go further by describing the shape or size of the returned comparison, but the key behavioral risk is disclosed.

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?

Two sentences, zero filler, with the scope and the authorization precondition front-loaded. Every clause carries information an agent needs before calling.

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 one-parameter read-only comparison with no output schema, the description covers what is compared and how failure behaves, which is close to sufficient. The remaining gap is the multi-ID string encoding and any hint about the comparison result's structure or size.

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% and robot_ids is an untyped-description string, so the description carries the burden. It usefully constrains the count to 2-5, which the schema does not enforce, but never explains how multiple IDs are encoded in a single string (delimiter, array serialization, ordering). The cardinality hint partially compensates for the coverage gap but leaves the actual encoding ambiguous.

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?

States a specific verb (compare), resource (robots), cardinality (2 to 5), and the exact comparison dimensions (BOM, metrics, risk, geographic exposure). The word 'semiconductor' in the body and title cleanly separates it from the mechanical_compare_robots and software_compare_robots 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?

Gives the operating envelope — 2 to 5 robots and an access right required on every listed robot — which tells the agent when the call is valid. It stops short of routing guidance (e.g., use hardware_get_robot for a single robot, or list_robots to discover IDs), so alternatives are implied rather than named.

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