stm32_get_system_status

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

With no annotations, the description carries the full burden of behavioral transparency. It does disclose what the tool checks and gives concrete categories of information, implying a non-mutating status read. However, it does not explicitly state that the tool has no side effects, what happens if the IDE is not running, or whether any process scan could be expensive or require permissions.

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 concise and well-structured: an introductory sentence followed by four focused bullet points. It is front-loaded with the main purpose and every line adds meaningful information without filler.

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?

The description covers the main facets of the tool's behavior and an output schema exists to define return structure. However, given the large sibling set with overlapping functionality, it lacks guidance on when to use this tool instead of focused alternatives, and it omits details about edge cases such as the IDE not running or no probes connected.

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?

The tool takes zero parameters, so there are no parameter semantics to clarify. The schema coverage is complete and the description's enumeration of output categories helps set expectations for what the returned status will contain.

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 that the tool checks the real-time operational status of STM32CubeIDE and enumerates the status categories: GUI state, process metrics, open windows, and connected debug probes. It is a specific verb+resource statement, though it does not explicitly differentiate itself from overlapping siblings like stm32_list_connected_probes or stm32_get_ide_windows.

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?

No guidance is given on when to use this aggregate status tool versus the more specific sibling tools. There are no usage conditions, exclusions, or alternatives mentioned, leaving the agent to infer when this tool should be preferred.

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