get_mco2_on_pc9

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

The description discloses that the tool outputs a clock signal and is for advanced debugging. However, it ambiguously includes '[UINT8, default: OFF]' which is unclear whether it describes the return value or a parameter, and no annotations are provided to clarify safety or permissions.

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 short but the first clause repeats the tool name, and the bracketed note is ambiguous. It could be more efficiently written without redundancy.

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?

For a simple getter with no output schema, the description should clearly state what is returned. The '[UINT8, default: OFF]' hint at the value but is not explicit about whether it is the output or a setting. The tool's behavior and output format are insufficiently described.

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?

The input schema has zero parameters, yet the description includes '[UINT8, default: OFF]' which suggests a parameter, causing confusion. With 100% schema coverage (no params), the description adds misleading information instead of clarifying the absence of parameters.

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 it outputs the MCO2 clock signal on PC9 pin, which clearly identifies the tool's purpose. The 'Advanced hardware debugging only' qualifier adds context. However, it starts with 'Get mco2_on_pc9:' which is redundant with the tool name.

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 specifies 'Advanced hardware debugging only', which provides some guidance on when to use, but does not explicitly mention when not to use or suggest alternatives (though the sibling set_tool is implied).

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