mhs5200_set_offset

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

Adds significant behavioral context: explains formula, percentage interpretation, and return type (JSON confirmation). Annotations already hint idempotency and non-destructiveness; description reinforces without contradiction.

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?

Concise but includes necessary details like formula and examples. Well-structured with bullet points, though slightly verbose for a simple set operation.

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?

Covers purpose, parameter details, formula, range, and return value. Output schema is present but description still mentions return format, making it fully self-contained.

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?

Despite schema description coverage reported as 0%, the description extensively explains offset_percent with examples and formula, greatly adding meaning beyond the schema's basic range and default.

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?

Clearly states 'Set the DC offset for a channel.' Identifies verb (set) and resource (DC offset for a channel). Distinct from sibling tools which handle other parameters.

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 explains when to use (to adjust DC offset). Implicitly excludes other sibling tools by focusing on offset specific details, but lacks explicit 'when not to use' or direct comparisons.

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