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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world behavior, so the description need not repeat that. It adds the pre-check usage context but does not mention the return format (boolean) or any other behavioral detail. With annotations covering the safety profile, a 3 is appropriate.

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 contains no filler and delivers the essential purpose and usage context immediately.

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 boolean check with full annotation coverage and complete schema documentation, the description provides the purpose and usage context. It could explicitly state that it returns a boolean, but the name and 'Check whether' strongly imply that. Nothing critical is missing for an agent to call it correctly.

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?

There is one parameter (bookingUid) with 100% schema description coverage, so the schema fully documents it. The description adds no additional meaning beyond what the schema provides. Baseline 3 is correct.

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 a specific verb ('Check') and resource ('whether a booking already has a wrong-assignment report'), making the operation clear. It implicitly distinguishes from list_wrong_assignment_reports (which lists all) and report_wrong_assignment (which files one) via 'before filing another', though it does not explicitly name those siblings.

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 phrase 'before filing another' gives a clear, actionable context: use this tool as a pre-check prior to calling report_wrong_assignment. It does not explicitly state when not to use it or name an alternative, but the intended workflow is unambiguous.

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