call

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the risk profile is largely covered structurally. The description adds the delegation semantics ('Returns that tool's result') but does not warn that side effects depend entirely on the invoked tool or discuss auth/rate limits, so it adds only moderate context.

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?

One tight paragraph, front-loaded with the capability and immediately followed by the condition and a concrete example. Every sentence earns its place with no 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?

With no output schema, the description usefully notes that it returns the invoked tool's result, closing the biggest information gap. For a generic dispatcher the coverage is strong, though it could say more about how errors or destructive side effects from the delegated tool surface.

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 tool, args and session are all documented in the schema itself, which sets the baseline at 3. The description reinforces usage with a call(tool=..., args={...}) example but adds no syntax, format, or constraint detail beyond what the schema provides.

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 states a specific verb (invoke) and resource (ANY stm32-gdb-mcp tool by name) and makes the dispatch role explicit, which cleanly separates it from every concrete sibling like start_debug_session or read_memory. An agent immediately understands this is a meta-call escape hatch rather than a domain operation.

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?

It gives the selecting condition explicitly — use it when the target tool is 'NOT in your current tool list' because clients with tool-count limits may hide some — and provides a concrete example with start_debug_session. It stops short of stating when to prefer a directly-listed sibling over this generic path, which is the only gap.

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