set_system_hse_mhz

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

No annotations are provided, and the description does not disclose important behavioral aspects such as whether the change is immediate, persists across reboots, or requires a restart. The description only states what the tool does, not the implications.

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 very concise, two sentences plus a bracketed spec. It front-loads the key information and has no wasted words.

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?

Given the simplicity of the tool (single parameter, no output schema), the description covers the essential purpose and parameter semantics. However, it lacks behavioral context about persistence and side effects, which would be valuable for a setting tool.

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% with a description for the only parameter. The tool description adds meaning by explaining the physical significance ('External crystal frequency in MHz') and the special auto-detect behavior (0), going beyond the schema.

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 sets the external crystal frequency in MHz, specifying the resource and unit. It adds context about non-standard clock speeds, but does not explicitly differentiate from other set_* sibling tools.

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 mentions 'Required for some non-standard clock speeds' and 'Set to 0 for auto-detect', giving limited usage guidance. However, no alternatives or when-not-to-use conditions are provided, and the tool is straightforward.

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