Checks if FreeRTOS symbols are present in the current GDB debug session to determine whether RTOS-aware state inspection is available.
Detects whether FreeRTOS symbols are available in the current GDB session.
| Name | Required | Description | Default |
|---|---|---|---|
| session | No | Optional debug-session name. Omit for the default target. |
Changes observed during successful MCP inspections.
v0.15.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and closed-world behavior, so the safety profile is covered. The description adds session scoping but does not describe return shape, failure behavior, or prerequisites beyond that.
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?
A single front-loaded sentence with no filler. It communicates the essential purpose immediately.
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 detection tool, the purpose plus schema and annotations are nearly sufficient; the boolean-style result is implied by 'detects whether.' However, it does not explicitly state the return form or behavior when no session exists, leaving minor gaps.
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%, and the sole optional session parameter is fully documented in the schema. The description adds no extra meaning beyond what the schema already provides, so the baseline is 3.
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 and resource: detect FreeRTOS symbol availability. The scope, 'current GDB session,' makes it clearly distinct from siblings such as read_freertos or session diagnostics.
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 says what the tool does but not when to use it instead of alternatives like read_freertos or detect_probe. There is no explicit when-to-use, when-not-to-use, or prerequisite guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.