compliance

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

No annotations are provided, so the description carries the full behavioral burden. It never states that these are read-only audits with no project mutation, does not mention that checks can be long-running (the schema defaults timeout to 900s), and says nothing about failure semantics or what a failing check produces. The word 'checks' only weakly implies a non-mutating operation.

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?

A single front-loaded sentence that leads with the verb and then enumerates the checks; there is no filler. The dense list of seven items is slightly run-on but every clause maps to a real action value, so little is wasted.

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 5-parameter, enum-driven tool with no annotations and no output schema, the description covers what the checks are but not what they return, how failures surface, or how to pick between overlapping checks. It is adequate to invoke the tool but thin on outcomes for an audit-style operation.

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 description coverage is 100%, so action, project_id, ip, mode, and timeout are all documented in the schema; the baseline is 3. The description adds meaningful semantics for several action values (e.g. check_modes = mode availability for current pin map), but it does not state that check_mode consumes ip and mode, nor does it clarify the timeout tradeoff.

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 names a specific verb+resource ('Run CubeMX's own consistency checks') and enumerates the concrete check families: xts/xtest suites, check mcu modes, all-MCU mode and XML audits, single mode check, pinout keep-placement. This maps cleanly onto the action enum, so an agent can tell what the tool does without opening the schema. It stops short of differentiating from adjacent verification siblings (mode_check, verify, value_check).

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?

Enumerating the available checks implies when each action is relevant, and the parenthetical '(mode availability for the current pin map)' gives a usage cue for check_modes. However, there is no explicit when-to-use vs when-not guidance, and no routing to the near-duplicate siblings mode_check, verify, value_check, or standalone_validate.

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