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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the requirement for an access right on the robot, which is useful behavioral context not captured by annotations. It also indicates the analysis focuses on specific dependency aspects, but does not describe return format or pagination, which are not critical given the read-only nature.

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 two concise sentences, first stating the purpose and second noting the access requirement. No fluff or unnecessary detail, front-loaded and efficient.

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 read-only analysis tool with one parameter and no output schema, the description covers purpose, basis, and key aspects. It also notes the access requirement. It does not mention output format or explicitly differentiate from sibling dependency tools, but it is sufficiently complete for the given complexity.

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 parameter robot_id. The description implies the robot_id must be a valid robot on which the user has access rights, but it does not add format, constraints, or examples. This compensates partially for the lack of schema description but not fully.

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 provides geopolitical and supply chain dependency analysis for a single robot based on its semiconductor BOM. It lists specific aspects (geographic concentration, single-source exposure, export control) and distinguishes from sibling tools that cover other subsystems or general robot info.

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 gives a clear context: when you need semiconductor dependency analysis for one robot. However, it does not explicitly mention alternatives or when not to use it, though the scope is evident from the title and description.

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