dbgprobe.svd.write

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

No annotations exist, so description carries full burden. It states 'No read-modify-write — the entire register is overwritten,' which is a key behavioral trait. However, it does not disclose potential side effects, permissions, or error conditions, leaving gaps.

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?

Two sentences, no wasted words. Direct and front-loaded with the key information. Every sentence adds value.

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?

No output schema, no annotations. The description covers core behavior and differentiation but misses prerequisites (e.g., session must exist, target may need to be halted) and return/error info. Adequate but not complete.

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 67% (value and register have descriptions). The description adds no new meaning for register or value beyond what the schema provides, and session_id remains undocumented. Baseline 3 is appropriate.

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 tool writes a raw value to a full register, distinguishing it from field-level writes by mentioning svd.set_field as an alternative. The verb 'Write' and resource 'full register' are specific.

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?

Explicitly tells when to use (raw register write) and when not (field-level writes, use svd.set_field). Does not cover prerequisites like needing an active session or SVD attachment, but provides clear differentiation from a sibling.

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