swmgr

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

No annotations are provided, so the description carries the full behavioral burden. It says install/remove and repository/proxy changes occur, but does not disclose permissions required, whether removal is destructive, how license acceptance affects installation, what connectivity checks return, or how project state is affected.

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 compact sentence that front-loads the tool's role and lists the main actions without filler. It is slightly run-on and omits some enum actions, but it is efficient overall.

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?

This is a multi-action tool with seven parameters, no output schema, and no annotations. The description lists high-level actions but does not map actions to parameters, explain required project_id/action usage, clarify licence or timeout behavior, or describe what connection status/check returns.

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 100%, so all seven parameters are already documented in the schema, including action enums and target examples. The description reinforces the main action categories but adds no parameter-level semantics beyond the schema baseline.

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 names specific verbs and resources: refresh the package catalogue, install/remove STM32Cube firmware packages or CMSIS-Packs, change repository path/proxy, and check connectivity. It is clearly a software/package manager tool, but it does not explicitly differentiate itself from nearby siblings such as firmware_packages, pack_status, or xcubedl.

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 by the list of supported actions, but there is no explicit guidance on when to choose this tool versus alternatives like pack_status or firmware_packages. 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.