dbg_regs_named_remote

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

With no annotations, the description only states a basic read operation. It does not disclose error behavior, required permissions, or side effects. The description adds minimal behavioral context beyond the obvious.

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 concise sentence that front-loads the action and resource. Every word is necessary and no extraneous information.

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 is adequate for a simple read tool, especially since an output schema exists. However, it lacks context about remote debugging prerequisites or limitations, which would be useful given the 'remote' suffix in the name.

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 100%, and the description does not add extra meaning to parameters beyond what the schema provides. The parameter descriptions in the schema are clear, so baseline score applies.

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 action ('Get') and the resource ('selected registers for a specific thread ID'). It distinguishes from siblings like 'dbg_gpregs' which presumably gets general-purpose registers, though it does not explicitly mention the remote aspect.

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 on when to use this tool versus alternatives like 'dbg_regs_named' (non-remote) or 'dbg_gpregs'. The description does not mention context such as needing a remote connection.

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