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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the permission requirement ('Requires an access right on the robot requested') and the enumeration of what the analysis actually covers. That is real context beyond structured fields, though it doesn't say what happens when access is missing.

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 tight sentences: the analytical scope comes first, the access prerequisite second. No filler and nothing an agent must read past to find the core purpose.

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?

There is no output schema, and the description compensates by naming the analysis dimensions returned (geographic concentration, critical raw materials, single-source exposure). Combined with the access-right note, an agent has enough to call it and set expectations, with only the failure behavior for missing access left unstated.

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 the single robot_id parameter, so the description must carry the load. It conveys that the tool operates on exactly one robot and that a per-robot access right is checked, which implicitly clarifies robot_id semantics, but gives no format guidance or example.

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 (analysis) and resource (geopolitical and supply chain dependency profile) scoped to one robot and grounded in the mechanical BOM. The 'mechanical BOM' anchor implicitly distinguishes it from hardware_get_dependency_profile and software_get_dependency_profile, though no sibling is named explicitly.

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 the use case (assessing geographic concentration, critical raw materials, single-source exposure for one robot) and states a prerequisite (access right on the robot), but never says when to choose this over software_get_dependency_profile or hardware_get_dependency_profile. Routing must be inferred from the domain prefix and 'mechanical BOM'.

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