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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write-but-not-destructive profile is covered. The description adds a meaningful behavioral rule beyond the annotations: a mandatory confirmation step before committing. It still omits what happens on failure, duplicate handling (relevant given the unmentioned idempotencyKey), and permission needs.

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 short sentences with zero filler; the action statement comes first and the confirmation constraint follows immediately. Every clause earns its place.

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 an 8-parameter mutation tool with full schema coverage and an explicit non-destructive annotation, the description covers the essential action and the critical workflow constraint (confirmation). It is missing only secondary context such as response/failure behavior and idempotency handling, and there is no output schema requiring explanation.

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 all eight parameters (including confirm's dry-run semantics and idempotencyKey) are already documented in the schema. The description adds no extra meaning about product, dose, dates, or confirmation flow. Baseline 3 is appropriate when the schema does all the work.

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?

States a specific verb (Record) plus a concrete resource (mite treatment chemical or acid application), which clearly separates it from sibling logging tools like log_hive_inspection or log_honey_harvest. It does not explicitly name or exclude any sibling, but the named resource is specific enough that no confusion is likely.

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 gives one actionable precondition – ALWAYS ask for confirmation before writing – which is genuine usage guidance for a write tool. It says nothing about when to prefer this over alternatives such as log_hive_inspection, and no exclusions or context conditions are given, so usage is only implied.

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